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