Os 303650 303650
View line Os 303650
Alerts for train 303650
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 303650.
It does not run today
Last recorded run: Wednesday 23 September +3 min
The mini-map returns when the train runs
On-time · 30 days
0%
0/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
On-time · 90 days
0%
0/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
- Tue 22 Sept Max en route +9 min · last fix heading to — +9 min
- Mon 21 Sept Max en route +7 min · last fix heading to — +7 min
- Wed 23 Sept Max en route +4 min · last fix heading to — +3 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 0% · 0
- 3–10 min 100% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 0% M n=1
- 0% T n=1
- 0% W n=1
- — T n=0
- — F n=0
- — S n=0
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 23 Sept | — 15:06 | +3 min | +4 min |
| Tue 22 Sept | — 15:11 | +9 min | +9 min |
| Mon 21 Sept | — 15:10 | +7 min | +7 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.