Os 305045 305045
View line Os 305045
Alerts for train 305045
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Os 305045.
It does not run today
Last recorded run: Friday 11 September 0 min
The mini-map returns when the train runs
On-time · 30 days
67%
2/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
On-time · 90 days
80%
4/5 runs under 3 min
RT coverage: 5 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
P90
+11min
9 in 10 runs arrive with less than this
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 10 Sept Max en route +18 min · last fix heading to — +18 min
Distribution · 90 days
5 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 80% · 4
- 3–10 min 0% · 0
- 10–30 min 20% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=1
- 100% W n=1
- 0% T n=1
- 100% F n=1
- — S n=0
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 11 Sept | — 00:29 | 0 min | — |
| Thu 10 Sept | — 00:13 | +18 min | +18 min |
| Wed 9 Sept | — 23:55 | 0 min | — |
| Tue 8 Sept | — 23:51 | 0 min | — |
| Mon 7 Sept | — 23:53 | 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.