Govia Thameslink Railway 871Z02

View line Govia Thameslink Railway

Mon Govia Thameslink Railway

It does not run today

Last recorded run: Monday 26 October +5 min

The mini-map returns when the train runs
On-time · 30 days
—
Too little data (1/1 runs with data)
RT coverage: 1 full · 0 partial · 0 no data
On-time · 90 days
33%
2/6 runs under 3 min
RT coverage: 6 full · 0 partial · 0 no data
Typical delay
+9min
Median at arrival, 90 days
P90
+30min
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 16 Aug Max en route +46 min · last fix heading to Hastings +46 min
  • Sun 9 Aug Max en route +15 min · last fix heading to Hastings +14 min
  • Mon 28 Sept Max en route +13 min · last fix heading to 87700 +13 min
  • Mon 26 Oct Max en route +5 min · last fix heading to Brighton +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 33% · 2
  • 3–10 min 17% · 1
  • 10–30 min 33% · 2
  • 30+ min 17% · 1

On-time by weekday

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

Recent runs

DateLast stopFinalMax
Mon 26 OctBrighton 04:50+5 min+5 min
Mon 28 Sept87700 11:50+13 min+13 min
Sat 19 SeptPortsmouth Harbour 09:31+1 min+3 min
Sat 12 SeptPortsmouth Harbour 09:290 min+3 min
Sun 16 AugHastings 19:23+46 min+46 min
Sun 9 AugHastings 18:51+14 min+15 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.