L2 2810
View line L2
Alerts for train 2810
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line L2.
It does not run today
Last recorded run: Wednesday 23 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
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
- 100% M n=1
- 100% T n=1
- 100% W n=2
- โ T n=0
- โ F n=0
- โ S n=0
- โ S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 23 Sept | โ 06:15 | 0 min | โ |
| Mon 21 Sept | โ 06:16 | 0 min | โ |
| Tue 15 Sept | โ 05:53 | 0 min | โ |
| Wed 12 Aug | โ 06:17 | 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.