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