GWR 742R49
View line GWR
Alerts for train 742R49
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.
The mini-map returns when the train runs
On-time · 30 days
33%
1/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
On-time · 90 days
60%
3/5 runs under 3 min
RT coverage: 5 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
P90
+4min
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
- Sun 18 Oct Max en route +5 min · last fix heading to Pangbourne +4 min
- Sun 20 Sept Max en route +4 min · last fix heading to 74260 +4 min
Distribution · 90 days
5 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 60% · 3
- 3–10 min 40% · 2
- 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
- 60% S n=5
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 18 Oct | Pangbourne 12:49 | +4 min | +5 min |
| Sun 27 Sept | 74260 12:45 | 0 min | +2 min |
| Sun 20 Sept | 74260 12:48 | +4 min | +4 min |
| Sun 13 Sept | 74260 12:44 | −1 min | — |
| Sun 6 Sept | 74260 12:44 | −1 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.