Os 13010 13010 Zábřeh na Moravě – Šumperk

View line Os 13010

Zábřeh na Moravě 08:26 → Šumperk 08:50 Mon, Tue, Wed, Thu, Fri 0 h 24 min · 5 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Thursday 12 November No data

Next service: today 08:26 from Zábřeh na Moravě · Fri 13 Nov

Next departure 08:26 today · Zábřeh na Moravě
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
83%
29/35 runs under 3 min
RT coverage: 35 full · 0 partial · 27 no data
Typical delay
−2min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

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

  • Thu 1 Oct Max en route +9 min · last fix heading to — +9 min
  • Fri 2 Oct Max en route +6 min · last fix heading to — +6 min
  • Mon 21 Sept Max en route +4 min · last fix heading to — +4 min
  • Tue 29 Sept Max en route +3 min · last fix heading to — +3 min
  • Thu 24 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

35 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 51% · 18
  • On time 31% · 11
  • 3–10 min 17% · 6
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 86% T n=7
  • 86% W n=7
  • 71% T n=7
  • 86% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 stops).

Last 90 days, 35 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.

StopSched.Usually 9 days in 10
08:26+2 min +7 min
08:28 / 08:29≈ +2 min ≈ +6 min
08:33≈ +2 min ≈ +5 min
08:36 / 08:44≈ +1 min ≈ +4 min
08:502 min early +3 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

DateLast stopFinalMax
Thu 12 NovŠumperk 08:49No data—
Wed 11 NovŠumperk 08:49No data—
Tue 10 NovŠumperk 08:49No data—
Mon 9 NovŠumperk 08:49No data—
Fri 6 NovŠumperk 08:49No data—
Thu 5 NovŠumperk 08:49No data—
Wed 4 NovŠumperk 08:49No data—
Tue 3 NovŠumperk 08:49No data—
Mon 2 NovŠumperk 08:49No data—
Fri 30 OctŠumperk 08:51No data—
Thu 29 OctŠumperk 08:51No data—
Tue 27 OctŠumperk 08:51No data—
Mon 26 OctŠumperk 08:51No data—
Fri 23 OctŠumperk 08:51No data—
Thu 22 OctŠumperk 08:52No data—
Wed 21 OctŠumperk 08:51No data—
Tue 20 OctŠumperk 08:51No data—
Mon 19 OctŠumperk 08:51No data—
Fri 16 OctŠumperk 08:52No data—
Thu 15 OctŠumperk 08:52No data—
Wed 14 OctŠumperk 08:51No data—
Tue 13 OctŠumperk 08:51No data—
Mon 12 OctŠumperk 08:51No data—
Fri 9 OctŠumperk 08:51No data—
Thu 8 OctŠumperk 08:51No data—
Wed 7 OctŠumperk 08:51No data—
Tue 6 OctŠumperk 08:51No data—
Mon 5 Oct— 08:550 min—
Fri 2 Oct— 09:01+6 min+6 min
Thu 1 Oct— 09:03+9 min+9 min