Govia Thameslink Railway 542C22

View line Govia Thameslink Railway

Sun Govia Thameslink Railway

It does not run today

Last recorded run: Sunday 18 October +5 min

The mini-map returns when the train runs
On-time · 30 days
50%
2/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
80%
8/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

  • Sun 18 Oct Max en route +8 min · last fix heading to Foxton +5 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Foxton +3 min

Distribution · 90 days

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

  • Early 30% · 3
  • On time 50% · 5
  • 3–10 min 20% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Recent runs

DateLast stopFinalMax
Sun 18 OctFoxton 12:50+5 min+8 min
Sun 11 OctFoxton 12:48+3 min+5 min
Sun 4 Oct47250 12:44−1 min+2 min
Sun 27 Sept47250 12:43−2 min+3 min
Sun 20 Sept47250 12:440 min+2 min
Sun 13 Sept47250 12:42−3 min+1 min
Sun 6 Sept47250 12:450 min+3 min
Sun 16 Aug47250 12:450 min+3 min
Sun 2 Aug47250 12:42−3 min+1 min
Sun 26 Jul47250 12:450 min+3 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.