L1 2217
View line L1
Alerts for train 2217
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line L1.
It does not run today
Last recorded run: Thursday 17 September 0 min
The mini-map returns when the train runs
On-time · 30 days
100%
3/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
On-time · 90 days
86%
6/7 runs under 3 min
RT coverage: 7 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
P90
+7min
9 in 10 runs arrive with less than this
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
- Mon 10 Aug Max en route +17 min · last fix heading to — +15 min
Distribution · 90 days
7 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 86% · 6
- 3–10 min 0% · 0
- 10–30 min 14% · 1
- 30+ min 0% · 0
On-time by weekday
- 0% M n=1
- 100% T n=1
- 100% W n=1
- 100% T n=2
- 100% F n=1
- — S n=0
- 100% S n=1
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 17 Sept | — 10:25 | 0 min | +2 min |
| Fri 11 Sept | — 10:30 | +2 min | +4 min |
| Wed 9 Sept | — 10:25 | 0 min | +2 min |
| Thu 27 Aug | — 10:25 | 0 min | +2 min |
| Tue 25 Aug | — 10:25 | 0 min | +3 min |
| Sun 23 Aug | — 10:24 | 0 min | +2 min |
| Mon 10 Aug | — 10:40 | +15 min | +17 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.