West Midlands Trains 651F67
View line West Midlands Trains
Alerts for train 651F67
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line West Midlands Trains.
The mini-map returns when the train runs
On-time · 30 days
72%
18/25 runs under 3 min
RT coverage: 25 full · 0 partial · 0 no data
On-time · 90 days
73%
53/73 runs under 3 min
RT coverage: 73 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+12min
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
- Mon 10 Aug Max en route +54 min · last fix heading to 42128 +51 min
- Thu 20 Aug Max en route +46 min · last fix heading to 36401 +42 min
- Wed 19 Aug Max en route +35 min · last fix heading to 36056 +29 min
- Sat 15 Aug Max en route +29 min · last fix heading to 36056 +24 min
- Thu 15 Oct Max en route +13 min · last fix heading to Wolverhampton +13 min
Distribution · 90 days
73 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 38% · 28
- On time 34% · 25
- 3–10 min 15% · 11
- 10–30 min 10% · 7
- 30+ min 3% · 2
On-time by weekday
- 69% M n=13
- 77% T n=13
- 85% W n=13
- 60% T n=10
- 83% F n=12
- 58% S n=12
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 21 Oct | Wolverhampton 19:55 | −2 min | +3 min |
| Tue 20 Oct | Wolverhampton 20:02 | +5 min | +5 min |
| Mon 19 Oct | Wolverhampton 19:57 | −1 min | +3 min |
| Sat 17 Oct | Wolverhampton 19:58 | +3 min | +7 min |
| Fri 16 Oct | Wolverhampton 19:59 | +3 min | +8 min |
| Thu 15 Oct | Wolverhampton 20:09 | +13 min | +13 min |
| Wed 14 Oct | Wolverhampton 19:55 | −2 min | +2 min |
| Tue 13 Oct | Wolverhampton 19:56 | −1 min | +2 min |
| Mon 12 Oct | Wolverhampton 19:57 | 0 min | +3 min |
| Sat 10 Oct | Wolverhampton 19:59 | +1 min | +6 min |
| Fri 9 Oct | Wolverhampton 19:56 | −1 min | +4 min |
| Thu 8 Oct | Wolverhampton 19:56 | 0 min | +6 min |
| Wed 7 Oct | Wolverhampton 19:57 | 0 min | +5 min |
| Tue 6 Oct | Wolverhampton 20:00 | +4 min | +10 min |
| Mon 5 Oct | Wolverhampton 19:54 | −2 min | +1 min |
| Sat 3 Oct | 36056 19:52 | −6 min | +3 min |
| Fri 2 Oct | 36056 19:54 | −2 min | +4 min |
| Thu 1 Oct | 36056 19:58 | +1 min | +7 min |
| Wed 30 Sept | 36056 19:55 | −2 min | +4 min |
| Tue 29 Sept | 36056 19:58 | +2 min | +6 min |
| Mon 28 Sept | 36056 20:02 | +4 min | +9 min |
| Sat 26 Sept | 36056 19:54 | −4 min | +4 min |
| Fri 25 Sept | 36056 19:57 | +1 min | +1 min |
| Thu 24 Sept | 36056 20:04 | +7 min | +14 min |
| Wed 23 Sept | 36056 19:59 | +2 min | +5 min |
| Tue 22 Sept | 36056 19:55 | −2 min | +4 min |
| Mon 21 Sept | 36056 20:03 | +5 min | +10 min |
| Fri 18 Sept | 36056 19:54 | −2 min | +6 min |
| Thu 17 Sept | 36056 20:04 | +7 min | +13 min |
| Wed 16 Sept | 36056 19:55 | −2 min | +3 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.