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