GWR 832C66
View line GWR
Alerts for train 832C66
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.
Not running right now
Last recorded run: Friday 18 September +10 min
The mini-map returns when the train runs
On-time · 30 days
—
Too little data (0/0 runs with data)
RT coverage: 0 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
- Tue 15 Sept Max en route +40 min · last fix heading to 83109 +40 min
- Fri 18 Sept Max en route +12 min · last fix heading to 83109 +10 min
Distribution · 90 days
4 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 25% · 1
- On time 25% · 1
- 3–10 min 0% · 0
- 10–30 min 25% · 1
- 30+ min 25% · 1
On-time by weekday
- — M n=0
- 0% T n=1
- 100% W n=1
- 100% T n=1
- 0% F n=1
- — S n=0
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 18 Sept | 83109 02:31 | +10 min | +12 min |
| Thu 17 Sept | 83109 02:19 | −2 min | — |
| Wed 16 Sept | 83109 02:22 | +1 min | +3 min |
| Tue 15 Sept | 83109 03:02 | +40 min | +40 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.