Govia Thameslink Railway 871H40
View line Govia Thameslink Railway
Alerts for train 871H40
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.
The mini-map returns when the train runs
On-time · 30 days
55%
12/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
58%
42/72 runs under 3 min
RT coverage: 72 full · 0 partial · 0 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+16min
9 in 10 runs arrive with less than this
30 days: +15 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
- Sat 22 Aug Max en route +27 min · last fix heading to 87972 +27 min
- Fri 21 Aug Max en route +29 min · last fix heading to 87959 +27 min
- Fri 25 Sept Max en route +28 min · last fix heading to 87959 +22 min
- Tue 8 Sept Max en route +32 min · last fix heading to 87959 +22 min
- Thu 13 Aug Max en route +21 min · last fix heading to 87959 +21 min
Distribution · 90 days
72 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 14% · 10
- On time 44% · 32
- 3–10 min 25% · 18
- 10–30 min 17% · 12
- 30+ min 0% · 0
On-time by weekday
- 85% M n=13
- 54% T n=13
- 69% W n=13
- 83% T n=12
- 25% F n=12
- 22% S n=9
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 15 Oct | Angmering 17:40 | −2 min | +2 min |
| Wed 14 Oct | Goring-by-Sea 17:47 | +5 min | +6 min |
| Tue 13 Oct | Angmering 17:41 | −1 min | +1 min |
| Mon 12 Oct | Angmering 17:44 | +1 min | +5 min |
| Fri 9 Oct | Goring-by-Sea 17:53 | +11 min | +12 min |
| Thu 8 Oct | Three Bridges 17:14 | −28 min | +1 min |
| Wed 7 Oct | Angmering 17:43 | +1 min | +1 min |
| Tue 6 Oct | Goring-by-Sea 17:48 | +6 min | +8 min |
| Mon 5 Oct | Angmering 17:44 | +2 min | +3 min |
| Sat 3 Oct | 87959 17:55 | +15 min | +17 min |
| Fri 2 Oct | 87959 17:44 | +2 min | +3 min |
| Thu 1 Oct | 87959 17:42 | −1 min | +4 min |
| Wed 30 Sept | 87959 18:00 | +18 min | +19 min |
| Tue 29 Sept | 87959 17:52 | +10 min | +10 min |
| Mon 28 Sept | 87959 17:42 | −1 min | +4 min |
| Sat 26 Sept | 87959 17:44 | +4 min | +4 min |
| Fri 25 Sept | 87959 18:05 | +22 min | +28 min |
| Thu 24 Sept | 87959 17:43 | +1 min | +4 min |
| Wed 23 Sept | 87959 17:41 | −1 min | +3 min |
| Tue 22 Sept | 87959 17:40 | −2 min | +3 min |
| Mon 21 Sept | 87959 17:50 | +7 min | +8 min |
| Fri 18 Sept | 87959 17:49 | +7 min | +9 min |
| Wed 16 Sept | 87959 17:41 | −2 min | +2 min |
| Tue 15 Sept | 87959 17:46 | +4 min | +6 min |
| Mon 14 Sept | 87959 17:45 | +2 min | +4 min |
| Fri 11 Sept | 87959 17:46 | +3 min | +5 min |
| Thu 10 Sept | 87959 17:44 | +2 min | +6 min |
| Wed 9 Sept | 87959 17:52 | +10 min | +12 min |
| Tue 8 Sept | 87959 18:05 | +22 min | +32 min |
| Mon 7 Sept | 87959 17:46 | +3 min | +5 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.