Govia Thameslink Railway 872Z48

View line Govia Thameslink Railway

Sat, Sun Govia Thameslink Railway

It does not run today

Last recorded run: Sunday 11 October 0 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
89%
8/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −2 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: −1 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 17 Aug Max en route +7 min · last fix heading to Eastbourne +3 min

Distribution · 90 days

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

  • Early 44% · 4
  • On time 44% · 4
  • 3–10 min 11% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 0% M n=1
  • 100% T n=1
  • 100% W n=1
  • — T n=0
  • — F n=0
  • 100% S n=2
  • 100% S n=4

Recent runs

DateLast stopFinalMax
Sun 11 OctBanstead 18:080 min+1 min
Sat 10 OctClapham Jn. C.S. 16:41−2 min+1 min
Sun 4 Oct87286 16:57−2 min—
Sat 3 Oct87286 16:42−2 min+1 min
Sun 27 Sept87286 16:55−2 min—
Sun 30 Aug87286 16:55−1 min+3 min
Wed 19 AugEastbourne 17:51+1 min+2 min
Tue 18 AugEastbourne 18:21+1 min+2 min
Mon 17 AugEastbourne 17:51+3 min+7 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.