Os 103110 103110
View line Os 103110
Alerts for train 103110
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 103110.
It does not run today
Last recorded run: Friday 2 October +2 min
The mini-map returns when the train runs
On-time · 30 days
50%
2/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
50%
2/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
Typical delay
—
Needs at least 5 runs with data (4 so far)
P90
—
Needs at least 5 runs with data (4 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 +8 min · last fix heading to — +8 min
- Fri 18 Sept Max en route +6 min · last fix heading to — +5 min
Distribution · 90 days
4 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 50% · 2
- 3–10 min 50% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- 50% T n=2
- 50% F n=2
- — S n=0
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 2 Oct | — 08:29 | +2 min | +2 min |
| Thu 1 Oct | — 08:25 | 0 min | — |
| Fri 18 Sept | — 08:30 | +5 min | +6 min |
| Thu 17 Sept | — 08:24 | +8 min | +8 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.