Govia Thameslink Railway 542D96

View line Govia Thameslink Railway

Mon Govia Thameslink Railway

It does not run today

Last recorded run: Monday 12 October 0 min

The mini-map returns when the train runs
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
90%
9/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

Last 30 days

Delay at the end of each run, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 3 Aug Max en route +27 min · last fix heading to Royston +26 min

Distribution · 90 days

10 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 20% · 2
  • On time 70% · 7
  • 3–10 min 0% · 0
  • 10–30 min 10% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 90% M n=10
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • — S n=0
  • — S n=0

Recent runs

DateLast stopFinalMax
Mon 12 OctRoyston 02:260 min+1 min
Mon 5 OctRoyston 02:25+1 min+1 min
Mon 21 SeptRoyston 02:23−2 min+3 min
Mon 14 SeptRoyston 02:24−2 min+2 min
Mon 7 SeptRoyston 02:260 min+2 min
Mon 24 AugRoyston 02:260 min+3 min
Mon 10 AugRoyston 02:27+1 min+2 min
Mon 3 AugRoyston 02:52+26 min+27 min
Mon 27 JulRoyston 02:250 min+1 min
Mon 20 JulRoyston 02:260 min+2 min

Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 11 July 2026.