REG 17501
Alerts for train 17501
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line REG.
Running now · updated 13:28
Running now +10 min
Today it is running worse than usual: typical arrival delay is +5 min; 0% of the last 5 runs arrived on time.
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 7 Nov Max en route +10 min · last fix heading to it-IMOLA +10 min
- Sat 24 Oct Max en route +10 min · last fix heading to it-IMOLA +9 min
- Sat 10 Oct Max en route +5 min · last fix heading to it-IMOLA +5 min
- Sat 31 Oct Max en route +7 min · last fix heading to it-IMOLA +4 min
- Sat 17 Oct Max en route +5 min · last fix heading to it-IMOLA +3 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 0% · 0
- 3–10 min 80% · 4
- 10–30 min 20% · 1
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 0% S n=5
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 7 Nov | it-IMOLA 13:24 | +10 min | +10 min |
| Sat 31 Oct | it-IMOLA 13:30 | +4 min | +7 min |
| Sat 24 Oct | it-IMOLA 13:35 | +9 min | +10 min |
| Sat 17 Oct | it-IMOLA 13:29 | +3 min | +5 min |
| Sat 10 Oct | it-IMOLA 13:31 | +5 min | +5 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.