REG 20119
View line REG
Alerts for train 20119
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
65%
17/26 runs under 3 min
RT coverage: 26 full · 0 partial · 0 no data
On-time · 90 days
70%
21/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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
- Thu 15 Oct Max en route +7 min · last fix heading to it-VELLETRI +7 min
- Wed 4 Nov Max en route +5 min · last fix heading to it-VELLETRI +5 min
- Mon 26 Oct Max en route +7 min · last fix heading to it-VELLETRI +5 min
- Mon 19 Oct Max en route +8 min · last fix heading to it-VELLETRI +5 min
- Thu 29 Oct Max en route +7 min · last fix heading to it-VELLETRI +4 min
Distribution · 90 days
30 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 10% · 3
- On time 60% · 18
- 3–10 min 30% · 9
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 50% M n=4
- 100% T n=5
- 50% W n=6
- 40% T n=5
- 80% F n=5
- 100% S n=5
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 7 Nov | it-VELLETRI 11:34 | +1 min | +2 min |
| Fri 6 Nov | it-VELLETRI 11:29 | −2 min | +2 min |
| Thu 5 Nov | it-VELLETRI 11:29 | +3 min | +7 min |
| Wed 4 Nov | it-VELLETRI 11:38 | +5 min | +5 min |
| Tue 3 Nov | it-VELLETRI 11:33 | 0 min | +3 min |
| Mon 2 Nov | it-VELLETRI 11:34 | +2 min | +4 min |
| Sat 31 Oct | it-VELLETRI 11:33 | 0 min | +1 min |
| Fri 30 Oct | it-VELLETRI 11:32 | −1 min | +4 min |
| Thu 29 Oct | it-VELLETRI 11:37 | +4 min | +7 min |
| Wed 28 Oct | it-VELLETRI 11:36 | +3 min | +8 min |
| Tue 27 Oct | it-VELLETRI 11:33 | 0 min | +5 min |
| Mon 26 Oct | it-VELLETRI 11:38 | +5 min | +7 min |
| Sat 24 Oct | it-VELLETRI 11:34 | +1 min | +3 min |
| Fri 23 Oct | it-VELLETRI 11:33 | 0 min | +6 min |
| Thu 22 Oct | it-VELLETRI 11:34 | +1 min | +3 min |
| Wed 21 Oct | it-VELLETRI 11:36 | +3 min | +7 min |
| Tue 20 Oct | it-VELLETRI 11:31 | −2 min | +2 min |
| Mon 19 Oct | it-VELLETRI 11:38 | +5 min | +8 min |
| Sat 17 Oct | it-VELLETRI 11:32 | −1 min | +3 min |
| Fri 16 Oct | it-VELLETRI 11:31 | −2 min | +6 min |
| Thu 15 Oct | it-VELLETRI 11:40 | +7 min | +7 min |
| Wed 14 Oct | it-VELLETRI 11:35 | +2 min | +7 min |
| Tue 13 Oct | it-VELLETRI 11:34 | +1 min | +3 min |
| Mon 12 Oct | it-VELLETRI 11:35 | +2 min | +6 min |
| Sat 10 Oct | it-VELLETRI 11:34 | +1 min | +4 min |
| Fri 9 Oct | it-VELLETRI 11:36 | +3 min | +4 min |
| Thu 8 Oct | it-VELLETRI 11:32 | −1 min | +6 min |
| Wed 7 Oct | it-VELLETRI 11:35 | +2 min | +6 min |
| Tue 6 Oct | it-VELLETRI 11:35 | +2 min | +5 min |
| Wed 16 Sept | it-VELLETRI 10:02 | 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.