R 90929 90929
View line R 90929
Alerts for train 90929
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 90929.
It does not run today
Last recorded run: Monday 5 October 0 min
The mini-map returns when the train runs
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 6 full · 0 partial · 0 no data
On-time · 90 days
100%
6/6 runs under 3 min
RT coverage: 6 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min
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
6 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 17% · 1
- On time 83% · 5
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- — T n=0
- — W n=0
- 100% T n=2
- 100% F n=1
- 100% S n=1
- 100% S n=1
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 5 Oct | — 16:19 | 0 min | — |
| Sun 4 Oct | — 16:14 | 0 min | — |
| Sat 3 Oct | — 16:16 | 0 min | — |
| Fri 2 Oct | — 16:42 | 0 min | — |
| Thu 1 Oct | — 16:23 | 0 min | — |
| Thu 17 Sept | — 18:25 | −8 min | +3 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.