Chiltern Railways 662L30
View line Chiltern Railways
Alerts for train 662L30
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Chiltern Railways.
The mini-map returns when the train runs
On-time · 30 days
—
Too little data (2/2 runs with data)
RT coverage: 2 full · 0 partial · 0 no data
On-time · 90 days
64%
7/11 runs under 3 min
RT coverage: 11 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+6min
9 in 10 runs arrive with less than this
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 5 Sept Max en route +7 min · last fix heading to Leamington Spa +7 min
- Sat 26 Sept Max en route +6 min · last fix heading to Leamington Spa +6 min
- Sat 29 Aug Max en route +5 min · last fix heading to Leamington Spa +4 min
- Sat 15 Aug Max en route +4 min · last fix heading to Leamington Spa +3 min
Distribution · 90 days
11 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 64% · 7
- 3–10 min 36% · 4
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 64% S n=11
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 24 Oct | Leamington Spa 10:15 | 0 min | +1 min |
| Sat 3 Oct | Leamington Spa 10:14 | −1 min | +1 min |
| Sat 26 Sept | Leamington Spa 10:21 | +6 min | +6 min |
| Sat 19 Sept | Leamington Spa 10:16 | +1 min | +2 min |
| Sat 12 Sept | Leamington Spa 10:15 | +1 min | +1 min |
| Sat 5 Sept | Leamington Spa 10:22 | +7 min | +7 min |
| Sat 29 Aug | Leamington Spa 10:19 | +4 min | +5 min |
| Sat 22 Aug | Leamington Spa 10:15 | +1 min | +2 min |
| Sat 15 Aug | Leamington Spa 10:17 | +3 min | +4 min |
| Sat 8 Aug | Leamington Spa 10:15 | 0 min | +1 min |
| Sat 1 Aug | Leamington Spa 10:15 | 0 min | +1 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.