Govia Thameslink Railway 882K13

View line Govia Thameslink Railway

Sun Govia Thameslink Railway

It does not run today

Last recorded run: Sunday 4 October 0 min

The mini-map returns when the train runs
On-time · 30 days
67%
2/3 runs under 3 min
RT coverage: 3 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
+5min
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 23 Aug Max en route +6 min · last fix heading to Brighton +6 min
  • Sun 20 Sept Max en route +5 min · last fix heading to Brighton +5 min

Distribution · 90 days

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

  • Early 10% · 1
  • On time 70% · 7
  • 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 4 OctBrighton 13:110 min—
Sun 27 SeptBrighton 13:11−1 min—
Sun 20 SeptBrighton 13:17+5 min+5 min
Sun 13 SeptBrighton 13:12+1 min+1 min
Sun 6 SeptBrighton 13:110 min—
Sun 30 AugBrighton 13:12+1 min+1 min
Sun 23 AugBrighton 13:17+6 min+6 min
Sun 9 AugBrighton 13:120 min—
Sun 2 Aug88404 19:36−2 min—
Sun 26 JulBrighton 13:01−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.