Govia Thameslink Railway 542P76

View line Govia Thameslink Railway

Mon Govia Thameslink Railway

✓ Today’s run finished

Today, last fix heading to Huntingdon at 02:17 −2 min

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

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 24 Aug Max en route +44 min · last fix heading to 45150 +23 min

Distribution · 90 days

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

  • Early 45% · 5
  • On time 45% · 5
  • 3–10 min 0% · 0
  • 10–30 min 9% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 91% M n=11
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • — S n=0
  • — S n=0

Recent runs

DateLast stopFinalMax
Mon 12 OctHuntingdon 02:17−2 min+2 min
Mon 5 Oct45150 01:58+2 min+2 min
Mon 28 Sept45150 02:10−3 min—
Mon 21 Sept45150 02:17−2 min+5 min
Mon 14 Sept45150 02:20+2 min+4 min
Mon 7 Sept45150 02:19+1 min+11 min
Mon 24 Aug45150 02:41+23 min+44 min
Mon 10 Aug45150 02:24+2 min+7 min
Mon 3 Aug45150 02:180 min+3 min
Mon 27 Jul45150 02:16−3 min+6 min
Mon 20 Jul45150 02:16−2 min+1 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.