R 301146 301146
View line R 301146
Alerts for train 301146
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 301146.
It does not run today
Last recorded run: Saturday 3 October +6 min
The mini-map returns when the train runs
On-time · 30 days
—
Too little data (1/1 runs with data)
RT coverage: 1 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
- Sat 3 Oct Max en route +6 min · last fix heading to — +6 min
- Tue 8 Sept Max en route +5 min · last fix heading to — +5 min
Distribution · 90 days
3 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 33% · 1
- 3–10 min 67% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- 0% T n=1
- 100% W n=1
- — T n=0
- — F n=0
- 0% S n=1
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 3 Oct | — 13:28 | +6 min | +6 min |
| Wed 9 Sept | — 13:06 | +1 min | +1 min |
| Tue 8 Sept | — 13:09 | +5 min | +5 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.