GWR 742N71
View line GWR
Alerts for train 742N71
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line GWR.
It does not run today
Last recorded run: Sunday 18 October +2 min
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
100%
5/5 runs under 3 min
RT coverage: 5 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
P90
+2min
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
Distribution · 90 days
5 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 40% · 2
- On time 60% · 3
- 3–10 min 0% · 0
- 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
- — S n=0
- 100% S n=5
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 18 Oct | Cholsey 20:02 | +2 min | +2 min |
| Sun 27 Sept | 74320 20:02 | +1 min | +1 min |
| Sun 20 Sept | 74320 19:59 | −2 min | +1 min |
| Sun 13 Sept | 74320 19:57 | −3 min | +1 min |
| Sun 6 Sept | 74320 19:59 | −1 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.