REG 20181
View line REG
Alerts for train 20181
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.
The mini-map returns when the train runs
On-time · 30 days
44%
12/27 runs under 3 min
RT coverage: 27 full · 0 partial · 0 no data
On-time · 90 days
52%
32/61 runs under 3 min
RT coverage: 61 full · 0 partial · 0 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +3 min
P90
+12min
9 in 10 runs arrive with less than this
30 days: +10 min
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 15 Jul Max en route +19 min · last fix heading to it-VELLETRI +19 min
- Sat 26 Sept Max en route +18 min · last fix heading to it-VELLETRI +18 min
- Wed 9 Sept Max en route +17 min · last fix heading to it-VELLETRI +17 min
- Sun 23 Aug Max en route +14 min · last fix heading to it-VELLETRI +14 min
- Tue 6 Oct Max en route +16 min · last fix heading to it-VELLETRI +13 min
Distribution · 90 days
61 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 52% · 32
- 3–10 min 33% · 20
- 10–30 min 15% · 9
- 30+ min 0% · 0
On-time by weekday
- 30% M n=10
- 60% T n=10
- 56% W n=9
- 56% T n=9
- 63% F n=8
- 43% S n=7
- 63% S n=8
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 9 Oct | it-VELLETRI 23:08 | +2 min | +4 min |
| Thu 8 Oct | it-VELLETRI 23:15 | +9 min | +14 min |
| Wed 7 Oct | it-VELLETRI 23:16 | +10 min | +11 min |
| Tue 6 Oct | it-VELLETRI 23:19 | +13 min | +16 min |
| Mon 5 Oct | it-VELLETRI 23:09 | +3 min | +9 min |
| Sat 3 Oct | it-VELLETRI 22:14 | +2 min | +2 min |
| Fri 2 Oct | it-VELLETRI 22:15 | −1 min | — |
| Thu 1 Oct | it-VELLETRI 22:16 | +3 min | +3 min |
| Wed 30 Sept | it-VELLETRI 22:16 | +2 min | +2 min |
| Tue 29 Sept | it-VELLETRI 22:15 | +4 min | +4 min |
| Mon 28 Sept | it-VELLETRI 22:15 | +3 min | +3 min |
| Sun 27 Sept | it-VELLETRI 22:15 | +2 min | +2 min |
| Sat 26 Sept | it-VELLETRI 22:29 | +18 min | +18 min |
| Fri 25 Sept | it-VELLETRI 22:24 | +11 min | +11 min |
| Thu 24 Sept | it-VELLETRI 22:14 | +2 min | +2 min |
| Wed 23 Sept | it-VELLETRI 22:17 | +1 min | +1 min |
| Tue 22 Sept | it-VELLETRI 22:30 | 0 min | — |
| Mon 21 Sept | it-VELLETRI 22:14 | +2 min | +3 min |
| Sun 20 Sept | it-VELLETRI 22:16 | +3 min | +3 min |
| Sat 19 Sept | it-VELLETRI 22:16 | +4 min | +4 min |
| Fri 18 Sept | it-VELLETRI 22:15 | +2 min | +2 min |
| Thu 17 Sept | it-VELLETRI 22:21 | +8 min | +8 min |
| Wed 16 Sept | it-VELLETRI 22:15 | +4 min | +4 min |
| Tue 15 Sept | it-VELLETRI 22:18 | +6 min | +6 min |
| Mon 14 Sept | it-VELLETRI 22:21 | +9 min | +9 min |
| Sun 13 Sept | it-VELLETRI 22:15 | +1 min | +1 min |
| Fri 11 Sept | it-VELLETRI 22:14 | 0 min | — |
| Thu 10 Sept | it-VELLETRI 22:14 | 0 min | — |
| Wed 9 Sept | it-VELLETRI 22:29 | +17 min | +17 min |
| Tue 8 Sept | it-VELLETRI 22:16 | +2 min | +2 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.