Sp 2022 2022 Olomouc hl. n. – Otrokovice
Alerts for train 2022
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Sp 2022.
It has not run yet today
Last recorded run: Wednesday 4 November No data
Next service: today 12:05 from Olomouc hl. n. · Thu 5 Nov
Last 30 days
Arrival delay at Otrokovice, 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 1 Sept Max en route +23 min · last fix heading to — +20 min
- Mon 17 Aug Max en route +19 min · last fix heading to — +17 min
- Wed 30 Sept Max en route +12 min · last fix heading to — +9 min
- Tue 25 Aug Max en route +11 min · last fix heading to — +9 min
- Fri 21 Aug Max en route +11 min · last fix heading to — +9 min
Distribution · 90 days
40 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 13% · 5
- On time 48% · 19
- 3–10 min 35% · 14
- 10–30 min 5% · 2
- 30+ min 0% · 0
On-time by weekday
- 50% M n=8
- 50% T n=8
- 63% W n=8
- 88% T n=8
- 50% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 40 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 12:05 | on time | +6 min | |
| 12:09 | ≈ +1 min | ≈ +6 min | |
| 12:12 | ≈ +1 min | ≈ +7 min | |
| 12:13 | ≈ +1 min | ≈ +7 min | |
| 12:17 / 12:20 | ≈ +1 min | ≈ +7 min | |
| 12:23 | ≈ +1 min | ≈ +8 min | |
| 12:25 | ≈ +1 min | ≈ +8 min | |
| 12:26 | ≈ +1 min | ≈ +8 min | |
| 12:29 / 12:30 | ≈ +1 min | ≈ +8 min | |
| 12:32 | ≈ +2 min | ≈ +8 min | |
| 12:35 | ≈ +1 min | ≈ +8 min | |
| 12:39 | +2 min | +9 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.
Will I make my connection?
Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.
Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 4 Nov | Otrokovice 12:39 | No data | — |
| Tue 3 Nov | Otrokovice 12:39 | No data | — |
| Mon 2 Nov | Otrokovice 12:39 | No data | — |
| Fri 30 Oct | Otrokovice 12:40 | No data | — |
| Thu 29 Oct | Otrokovice 12:40 | No data | — |
| Tue 27 Oct | Otrokovice 12:40 | No data | — |
| Mon 26 Oct | Otrokovice 12:40 | No data | — |
| Fri 23 Oct | Otrokovice 12:40 | No data | — |
| Thu 22 Oct | Otrokovice 12:40 | No data | — |
| Wed 21 Oct | Otrokovice 12:40 | No data | — |
| Tue 20 Oct | Otrokovice 12:40 | No data | — |
| Mon 19 Oct | Otrokovice 12:40 | No data | — |
| Fri 16 Oct | Otrokovice 12:40 | No data | — |
| Thu 15 Oct | Otrokovice 12:40 | No data | — |
| Wed 14 Oct | Otrokovice 12:40 | No data | — |
| Tue 13 Oct | Otrokovice 12:40 | No data | — |
| Mon 12 Oct | Otrokovice 12:40 | No data | — |
| Fri 9 Oct | Otrokovice 12:40 | No data | — |
| Thu 8 Oct | Otrokovice 12:40 | No data | — |
| Wed 7 Oct | Otrokovice 12:40 | No data | — |
| Tue 6 Oct | Otrokovice 12:40 | No data | — |
| Mon 5 Oct | — 12:54 | +1 min | +4 min |
| Fri 2 Oct | — 12:56 | +2 min | +4 min |
| Thu 1 Oct | — 12:54 | 0 min | +4 min |
| Wed 30 Sept | — 13:02 | +9 min | +12 min |
| Tue 29 Sept | — 12:55 | +2 min | +3 min |
| Fri 25 Sept | — 12:53 | 0 min | +3 min |
| Thu 24 Sept | — 12:52 | −2 min | — |
| Wed 23 Sept | — 12:52 | −2 min | +2 min |
| Tue 22 Sept | — 12:54 | 0 min | +3 min |