Govia Thameslink Railway 871H34
View line Govia Thameslink Railway
Alerts for train 871H34
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
46%
13/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
On-time · 90 days
45%
39/87 runs under 3 min
RT coverage: 87 full · 0 partial · 0 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +3 min
P90
+14min
9 in 10 runs arrive with less than this
30 days: +9 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
- Thu 13 Aug Max en route +34 min · last fix heading to 87959 +34 min
- Fri 21 Aug Max en route +34 min · last fix heading to 87959 +32 min
- Sat 5 Sept Max en route +30 min · last fix heading to 87959 +28 min
- Sat 22 Aug Max en route +27 min · last fix heading to 87972 +27 min
- Tue 25 Aug Max en route +25 min · last fix heading to 87959 +24 min
Distribution · 90 days
87 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 2% · 2
- On time 43% · 37
- 3–10 min 38% · 33
- 10–30 min 15% · 13
- 30+ min 2% · 2
On-time by weekday
- 62% M n=13
- 31% T n=13
- 62% W n=13
- 54% T n=13
- 31% F n=13
- 33% S n=9
- 38% S n=13
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 16 Oct | Goring-by-Sea 16:14 | +1 min | +2 min |
| Thu 15 Oct | Angmering 16:14 | +2 min | +3 min |
| Wed 14 Oct | Goring-by-Sea 16:17 | +5 min | +7 min |
| Tue 13 Oct | Angmering 16:22 | +10 min | +10 min |
| Mon 12 Oct | Goring-by-Sea 16:18 | +5 min | +7 min |
| Sun 11 Oct | Three Bridges 15:10 | +7 min | +7 min |
| Fri 9 Oct | Angmering 16:16 | +3 min | +6 min |
| Thu 8 Oct | Three Bridges 16:12 | −1 min | +24 min |
| Wed 7 Oct | Angmering 16:12 | −1 min | +1 min |
| Tue 6 Oct | Angmering 16:12 | −1 min | +1 min |
| Mon 5 Oct | Durrington-on-Sea 16:14 | +1 min | +3 min |
| Sun 4 Oct | 87927 16:14 | +2 min | +29 min |
| Sat 3 Oct | 87959 16:13 | +3 min | +4 min |
| Fri 2 Oct | 87959 16:12 | −1 min | +2 min |
| Thu 1 Oct | 87959 16:23 | +11 min | +12 min |
| Wed 30 Sept | 87959 16:12 | −1 min | +1 min |
| Tue 29 Sept | 87959 16:17 | +4 min | +8 min |
| Mon 28 Sept | 87959 16:16 | +3 min | +5 min |
| Sun 27 Sept | 87199 14:32 | +3 min | +3 min |
| Sat 26 Sept | 87959 16:14 | +3 min | +6 min |
| Fri 25 Sept | 87927 16:23 | +10 min | +33 min |
| Thu 24 Sept | 87959 16:13 | 0 min | +3 min |
| Wed 23 Sept | 87959 16:14 | +1 min | +7 min |
| Tue 22 Sept | 87959 16:14 | +2 min | +3 min |
| Mon 21 Sept | 87959 16:14 | +1 min | +3 min |
| Sun 20 Sept | 87959 16:27 | +9 min | +10 min |
| Fri 18 Sept | 87959 16:16 | +4 min | +6 min |
| Thu 17 Sept | Three Bridges 15:00 | +3 min | +3 min |
| Wed 16 Sept | 87959 16:13 | 0 min | +3 min |
| Tue 15 Sept | 87959 16:16 | +3 min | +4 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.