Great British rail train delays, Saturday 17 October 2026

Delays recorded on this day, in Great Britain local time. Below: how it went, then the whole day as one file to download.

Until 21 October 2026, Aubin's relay of National Rail's Darwin (frozen from 21 October 16:48 London time). From late October 2026, straight from Darwin's Push Port (data: National Rail, via the Rail Data Marketplace; not for commercial redistribution), matched to this timetable; actual times are marked apart from estimates.

How late the trains were

89% of stops were reached less than 5 minutes late, and half of them within 0 minutes of the timetable.

Trains
20,087
5 min late or more
11% of stops
15 min late or more
2% of stops
Median delay
0 min
Cancelled trains
393

Recorded from 00:00 to 23:59. The figures use the last delay announced at each of the 242,318 stops that had one, as the operator sent it. Cancelled trains (marked cancelled, or with every stop skipped), skipped stops and values over an hour early or twelve hours late are left out, as are 162 placeholder values the feed sent instead of a time (a train “here, now” hours late, or one time repeated at every stop). 100% of the stops of the trains that ran (skipped stops aside) had a delay.

The archive saw 20,019 of the 20,019 trains the timetable planned for this day.

Most delayed trains

LineLeft its first stopWhere it was latestDelay
ScotRailNorth Berwick250 min
TfW Rail Transport for WalesRadyr (Platform 3)142 min
GWR Great Western RailwayReading (Platform 5)139 min
TfW Rail Transport for WalesRadyr (Platform 3)137 min
TfW Rail Transport for WalesRadyr (Platform 3)129 min

Download

Read this day from code

This day’s table of final delays has a fixed address. Read it from DuckDB, Polars or curl, with one of your API tokens in place of YOUR_TOKEN:

https://data.train-archive.eu/daily/provider=gb-aubin/service=TripUpdate/date=2026-10-17.parquet?token=YOUR_TOKEN

Examples for this day Try it in your browser

A few rows of the file

15 different trains, each at one stop. The CSV has more columns, listed below.

Stop stop_nameLine routeArrival predicted_arrivalDelay (min) arrival_delay_minStatus trip_status
Woolwich (Platform B)Elizabeth line02:02-1added
Glasgow Central (Platform 5)ScotRail19:29-2scheduled
Ilkley (Platform 1)Northern22:481scheduled
Bristol Temple Meads (Platform 5)GWR Great Western Railway17:01-2scheduled
Birmingham New Street (Platform 10a)CrossCountry23:062scheduled
Crewe (Platform 9)TfW Rail Transport for Wales09:18-2scheduled
London Victoria (Platform 18)Southern22:1614scheduled
London Marylebone (Platform 5)Chiltern Railways08:59-1scheduled
Portsmouth Harbour (Platform 5)SWR South Western Railway08:520scheduled
Norwich (Platform 3b)Greater Anglia00:05-3scheduled
Faversham (Platform 4)Southeastern00:57-1scheduled
Dalston Junction (Platform 2)Windrush Windrush line19:127scheduled
Brighton (Platform 4)Thameslink14:480scheduled
Wemyss Bay (Platform 2)ScotRail19:45-1scheduled
Birmingham New Street (Platform 7M)WMR West Midlands Railway17:110scheduled

What the columns mean

service_date
The day the train was scheduled to run.
route
The line, as the operator names it (for example IC 3 or S2).
trip_id
The operator’s code for this train run. The same train on another day has another code.
trip_start_time
When the train was scheduled to leave its first station.
stop_sequence, stop_id, stop_name
Which stop along the route: its position, code and name.
arrival_delay_min, departure_delay_min
How late the train was at that stop, in minutes. Negative means early. Empty when the operator gave a time but no delay.
predicted_arrival, predicted_departure
The time the operator last announced for that stop, in local time.
observed_at
When that last announcement was seen. After the train has passed, it is what happened.
trip_status
scheduled, cancelled or added (a train that was not in the timetable).
stop_status
skipped when the train did not stop there; empty otherwise.
route_id
The route’s code in the timetable, to join with it.