Status
Feeds flowing, with open incidents
Live feeds
Where the data comes from
Darwin Live Departure Boards
last message 13 s ago · 25,022 archivedFlowing
last message 13 s ago · 25,022 archivedFlowing
Darwin Push Port (live train movements)
last message 0 s ago · 3,560,063 archivedFlowing
last message 0 s ago · 3,560,063 archivedFlowing
Network Rail TRUST (train positions)
not connected yetPlanned
not connected yetPlanned
Network Rail TD (signalling berths)
not connected yetPlanned
not connected yetPlanned
Timetable
How fresh the schedule is
The newest Darwin timetable drop was cut 4 days ago (69,014 journeys) and loaded 4 days ago. It is older than 36 hours, so some trains show as "towards" a destination until the next drop loads.
Data integrity
Open incidents
Rail checks its own data every five minutes for schema drift, distribution shifts and contradictions. 1 critical incident is open.
An estimate earlier than the previous actual departure522 warn
Reported on time but not moving in the data33 warn
A platform changed after arrival218 warn
A message we could not parse2 warn
A field is unexpectedly empty or unexpectedly full2 warn
An actual time on a cancelled service11 warn
The feed sent a field we have not seen before1 info
A record missing a required value1 warn
Timetable older than 36 hours1 critical
- An estimate earlier than the previous actual departure — uk:202609146738354: estimated arrival at SPNY205 (2026-09-14T05:41:00.000Z) is before the actual departure from the previous stop (2026-09-14T05:46:00.000Z)
since 5 h ago, seen 71× - An estimate earlier than the previous actual departure — uk:202609146734175: estimated arrival at QPRKJ (2026-09-14T08:54:00.000Z) is before the actual departure from the previous stop (2026-09-14T09:23:00.000Z)
since 1 h ago, seen 21× - An estimate earlier than the previous actual departure — uk:202609148965389: estimated arrival at ELLBNLL (2026-09-14T08:44:00.000Z) is before the actual departure from the previous stop (2026-09-14T09:24:00.000Z)
since 1 h ago, seen 21× - A platform changed after arrival — uk:202609147186329: platform at JAMESST changed after the train had already arrived (2026-09-14T05:51:00.000Z)
since 5 h ago, seen 71× - A platform changed after arrival — uk:202609148776307: platform at KEWGRDN changed after the train had already arrived (2026-09-14T09:25:00.000Z)
since 1 h ago, seen 21× - An actual time on a cancelled service — uk:202609146718640 is cancelled but FNPK (and maybe later stops) has an actual time
since 5 h ago, seen 72× - An estimate earlier than the previous actual departure — uk:202609146734148: estimated arrival at QPRKJ (2026-09-14T07:54:00.000Z) is before the actual departure from the previous stop (2026-09-14T08:22:00.000Z)
since 2 h ago, seen 36× - An estimate earlier than the previous actual departure — uk:202609148776372: estimated arrival at KEWGRDN (2026-09-14T08:18:00.000Z) is before the actual departure from the previous stop (2026-09-14T08:22:00.000Z)
since 2 h ago, seen 36×
Alerts
How fast a change reaches a phone
In the last 24 hours Rail sent 38 notifications. Half arrived within 206 ms of the feed message and 95% within 312 ms, measured from the moment the feed message was received to the moment the push left for Apple.