Govia Thameslink Railway 451P11
View line Govia Thameslink Railway
Alerts for train 451P11
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Govia Thameslink Railway.
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
100%
6/6 runs under 3 min
RT coverage: 6 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
P90
+2min
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
Distribution · 90 days
6 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 50% · 3
- On time 50% · 3
- 3–10 min 0% · 0
- 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
- 100% S n=6
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 8 Nov | Biggleswade 07:14 | +2 min | +2 min |
| Sun 27 Sept | 53231 07:55 | +2 min | +2 min |
| Sun 20 Sept | 54245 08:14 | −3 min | — |
| Sun 6 Sept | 54245 08:13 | −3 min | +1 min |
| Sun 23 Aug | Hitchin 07:36 | 0 min | — |
| Sun 16 Aug | 54245 08:13 | −3 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.