R 100952 100952
View line R 100952
Alerts for train 100952
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line R 100952.
It does not run today
Last recorded run: Monday 28 September +3 min
The mini-map returns when the train runs
On-time · 30 days
50%
2/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
50%
2/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
Worst days
- Mon 28 Sept Max en route +3 min · last fix heading to — +3 min
- Sun 27 Sept Max en route +3 min · last fix heading to — +3 min
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 50% · 2
- 3–10 min 50% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 0% M n=1
- — T n=0
- — W n=0
- — T n=0
- 100% F n=1
- 100% S n=1
- 0% S n=1
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 28 Sept | — 06:00 | +3 min | +3 min |
| Sun 27 Sept | — 06:02 | +3 min | +3 min |
| Sat 26 Sept | — 06:01 | +2 min | +2 min |
| Fri 25 Sept | — 06:02 | +1 min | +1 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.