REG 90038
View line REG
Alerts for train 90038
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.
Not running right now
Last recorded run: Tuesday 22 September 0 min
The mini-map returns when the train runs
On-time · 30 days
—
Too little data (1/1 runs with data)
RT coverage: 1 full · 0 partial · 0 no data
On-time · 90 days
100%
4/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
Distribution · 90 days
4 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 4
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- 100% T n=1
- — W n=0
- 100% T n=1
- — F n=0
- 100% S n=2
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Tue 22 Sept | it-BOLOGNA CENTRALE 00:29 | 0 min | — |
| Thu 17 Sept | it-BOLOGNA CENTRALE 00:29 | 0 min | — |
| Sat 12 Sept | it-BOLOGNA CENTRALE 00:29 | 0 min | — |
| Sat 5 Sept | it-BOLOGNA CENTRALE 00:30 | 0 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.