Os 13037 13037 Velké Losiny – Šumperk
Alerts for train 13037
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 13037.
It has not run yet today
Last recorded run: Friday 6 November No data
Next service: today 16:49 from Velké Losiny · Mon 9 Nov
Last 30 days
Arrival delay at Šumperk, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 2 Sept Max en route +6 min · last fix heading to — +6 min
- Mon 24 Aug Max en route +5 min · last fix heading to — +5 min
- Wed 30 Sept Max en route +4 min · last fix heading to — +4 min
- Fri 28 Aug Max en route +3 min · last fix heading to — +3 min
Distribution · 90 days
36 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 3% · 1
- On time 86% · 31
- 3–10 min 11% · 4
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 83% M n=6
- 100% T n=6
- 75% W n=8
- 100% T n=8
- 88% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 37 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 |
|---|---|---|---|
| 16:49 | on time | +2 min | |
| 16:50 | ≈ on time | ≈ +2 min | |
| 16:52 | ≈ on time | ≈ +2 min | |
| 16:54 | ≈ on time | ≈ +2 min | |
| 16:56 / 16:57 | ≈ on time | ≈ +2 min | |
| 16:59 | ≈ on time | ≈ +2 min | |
| 17:00 | ≈ on time | ≈ +2 min | |
| 17:02 | ≈ on time | ≈ +2 min | |
| 17:04 | on time | +2 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 |
|---|---|---|---|
| Fri 6 Nov | Šumperk 17:04 | No data | — |
| Thu 5 Nov | Šumperk 17:04 | No data | — |
| Wed 4 Nov | Šumperk 17:04 | No data | — |
| Tue 3 Nov | Šumperk 17:04 | No data | — |
| Mon 2 Nov | Šumperk 17:04 | No data | — |
| Fri 30 Oct | Šumperk 17:05 | No data | — |
| Thu 29 Oct | Šumperk 17:05 | No data | — |
| Tue 27 Oct | Šumperk 17:05 | No data | — |
| Mon 26 Oct | Šumperk 17:05 | No data | — |
| Fri 23 Oct | Šumperk 17:05 | No data | — |
| Thu 22 Oct | Šumperk 17:05 | No data | — |
| Wed 21 Oct | Šumperk 17:05 | No data | — |
| Tue 20 Oct | Šumperk 17:05 | No data | — |
| Mon 19 Oct | Šumperk 17:05 | No data | — |
| Fri 16 Oct | Šumperk 17:05 | No data | — |
| Thu 15 Oct | Šumperk 17:05 | No data | — |
| Wed 14 Oct | Šumperk 17:05 | No data | — |
| Tue 13 Oct | Šumperk 17:05 | No data | — |
| Mon 12 Oct | Šumperk 17:05 | No data | — |
| Fri 9 Oct | Šumperk 17:05 | No data | — |
| Thu 8 Oct | Šumperk 17:05 | No data | — |
| Wed 7 Oct | Šumperk 17:05 | No data | — |
| Tue 6 Oct | Šumperk 17:05 | No data | — |
| Mon 5 Oct | Šumperk 17:05 | No data | — |
| Fri 2 Oct | — 17:19 | +1 min | +1 min |
| Thu 1 Oct | — 17:20 | +2 min | +2 min |
| Wed 30 Sept | — 17:23 | +4 min | +4 min |
| Tue 29 Sept | — 17:19 | 0 min | — |
| Fri 25 Sept | — 17:19 | 0 min | — |
| Thu 24 Sept | — 17:18 | 0 min | — |