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