R 10301 10301
View line R 10301
Alerts for train 10301
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 10301.
It does not run today
Last recorded run: Saturday 19 September −3 min
The mini-map returns when the train runs
On-time · 30 days
—
Too little data (2/2 runs with data)
RT coverage: 2 full · 0 partial · 0 no data
On-time · 90 days
33%
1/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
Typical delay
—
Needs at least 5 runs with data (3 so far)
P90
—
Needs at least 5 runs with data (3 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
- Thu 17 Sept Max en route +10 min · last fix heading to — +10 min
- Sat 12 Sept Max en route +14 min · last fix heading to — +6 min
Distribution · 90 days
3 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 33% · 1
- On time 0% · 0
- 3–10 min 33% · 1
- 10–30 min 33% · 1
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- 0% T n=1
- — F n=0
- 50% S n=2
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 19 Sept | — 10:28 | −3 min | +4 min |
| Thu 17 Sept | — 20:37 | +10 min | +10 min |
| Sat 12 Sept | — 13:32 | +6 min | +14 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.