West Midlands Trains 652T03
View line West Midlands Trains
Alerts for train 652T03
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
67%
2/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
On-time · 90 days
50%
2/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
Typical delay
—
Needs at least 5 runs with data (4 so far)
P90
—
Needs at least 5 runs with data (4 so far)
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 10 Oct Max en route +13 min · last fix heading to — +9 min
- Mon 31 Aug Max en route +8 min · last fix heading to 65625 +8 min
Distribution · 90 days
4 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 50% · 2
- 3–10 min 50% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 0% M n=1
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 50% S n=2
- 100% S n=1
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 10 Oct | — 18:19 | +9 min | +13 min |
| Sun 13 Sept | — 10:57 | +2 min | +2 min |
| Sat 12 Sept | 65625 18:11 | +2 min | +2 min |
| Mon 31 Aug | 65625 23:34 | +8 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.