Govia Thameslink Railway 871H52
View line Govia Thameslink Railway
Alerts for train 871H52
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
63%
15/24 runs under 3 min
RT coverage: 24 full · 0 partial · 0 no data
On-time · 90 days
56%
40/72 runs under 3 min
RT coverage: 72 full · 0 partial · 0 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +1 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
- Mon 3 Aug Max en route +61 min · last fix heading to 87959 +55 min
- Thu 3 Sept Max en route +49 min · last fix heading to 87959 +35 min
- Tue 1 Sept Max en route +38 min · last fix heading to 87959 +29 min
- Thu 13 Aug Max en route +26 min · last fix heading to 87959 +25 min
- Sat 29 Aug Max en route +47 min · last fix heading to 87927 +21 min
Distribution · 90 days
72 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 15% · 11
- On time 40% · 29
- 3–10 min 24% · 17
- 10–30 min 18% · 13
- 30+ min 3% · 2
On-time by weekday
- 62% M n=13
- 46% T n=13
- 75% W n=12
- 36% T n=11
- 62% F n=13
- 50% S n=10
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Tue 20 Oct | Angmering 21:01 | +17 min | +17 min |
| Mon 19 Oct | Goring-by-Sea 20:42 | −2 min | +3 min |
| Sat 17 Oct | Angmering 20:41 | 0 min | +2 min |
| Fri 16 Oct | Angmering 20:43 | −1 min | +4 min |
| Thu 15 Oct | Angmering 20:48 | +4 min | +4 min |
| Wed 14 Oct | Angmering 20:45 | 0 min | +6 min |
| Tue 13 Oct | Angmering 21:00 | +16 min | +16 min |
| Mon 12 Oct | Goring-by-Sea 20:43 | −2 min | +1 min |
| Fri 9 Oct | Angmering 20:48 | +3 min | +5 min |
| Thu 8 Oct | Goring-by-Sea 20:42 | −2 min | +3 min |
| Wed 7 Oct | Angmering 20:46 | +2 min | +3 min |
| Tue 6 Oct | Goring-by-Sea 20:43 | −2 min | +3 min |
| Mon 5 Oct | Angmering 21:01 | +17 min | +24 min |
| Sat 3 Oct | 87959 20:32 | +1 min | +2 min |
| Fri 2 Oct | 87959 20:46 | +2 min | +4 min |
| Thu 1 Oct | 87959 20:50 | +6 min | +6 min |
| Wed 30 Sept | 87959 21:01 | +17 min | +17 min |
| Tue 29 Sept | 87959 20:47 | +3 min | +7 min |
| Mon 28 Sept | 87959 20:43 | −2 min | +3 min |
| Sat 26 Sept | 87959 20:42 | +1 min | +4 min |
| Fri 25 Sept | 87959 20:46 | 0 min | +6 min |
| Thu 24 Sept | 87959 20:43 | −2 min | +3 min |
| Wed 23 Sept | 87959 20:45 | 0 min | +4 min |
| Tue 22 Sept | 87959 20:49 | +5 min | +6 min |
| Mon 21 Sept | 87959 20:49 | +5 min | +8 min |
| Fri 18 Sept | 87959 20:46 | +2 min | +5 min |
| Wed 16 Sept | 87959 20:44 | 0 min | +8 min |
| Tue 15 Sept | 87959 20:43 | −1 min | +4 min |
| Mon 14 Sept | 87959 20:43 | −1 min | +2 min |
| Fri 11 Sept | 87959 20:52 | +7 min | +8 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.