GWR 742D79
View line GWR
Alerts for train 742D79
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
0%
0/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
On-time · 90 days
0%
0/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
Typical delay
—
Needs at least 5 runs with data (3 so far)
P90
—
Needs at least 5 runs with data (3 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
- Wed 4 Nov Max en route +15 min · last fix heading to Cholsey +15 min
- Thu 5 Nov Max en route +7 min · last fix heading to Cholsey +6 min
- Fri 6 Nov Max en route +4 min · last fix heading to Cholsey +4 min
Distribution · 90 days
3 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 0% · 0
- 3–10 min 67% · 2
- 10–30 min 33% · 1
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- 0% W n=1
- 0% T n=1
- 0% F n=1
- — S n=0
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 6 Nov | Cholsey 20:47 | +4 min | +4 min |
| Thu 5 Nov | Cholsey 20:49 | +6 min | +7 min |
| Wed 4 Nov | Cholsey 20:58 | +15 min | +15 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.