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

View line Os 13014

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

✓ Today’s run finished

Today, last fix heading to Šumperk at 14:48 No data

  1. Zábřeh na Moravě14:26
  2. Zábřeh na Moravě zastávka14:28
  3. Postřelmov14:33
  4. Bludov14:36
  5. Šumperk14:47

Next service: Wednesday 14:26 from Zábřeh na Moravě · Wed 18 Nov

Next departure 14:26 Wednesday · 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
67%
22/33 runs under 3 min
RT coverage: 33 full · 0 partial · 29 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+7min
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

  • Wed 30 Sept Max en route +9 min · last fix heading to — +9 min
  • Wed 23 Sept Max en route +7 min · last fix heading to — +7 min
  • Tue 22 Sept Max en route +8 min · last fix heading to — +7 min
  • Wed 9 Sept Max en route +14 min · last fix heading to — +7 min
  • Fri 2 Oct Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 21% · 7
  • On time 45% · 15
  • 3–10 min 33% · 11
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 50% T n=6
  • 57% W n=7
  • 86% T n=7
  • 57% 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, 33 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
14:26+4 min +8 min
14:28 / 14:29≈ +4 min ≈ +7 min
14:33≈ +3 min ≈ +6 min
14:36 / 14:41≈ +2 min ≈ +6 min
14:47+1 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.

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
Mon 16 NovŠumperk 14:48No data—
Fri 13 NovŠumperk 14:48No data—
Thu 12 NovŠumperk 14:48No data—
Wed 11 NovŠumperk 14:48No data—
Tue 10 NovŠumperk 14:48No data—
Mon 9 NovŠumperk 14:48No data—
Fri 6 NovŠumperk 14:48No data—
Thu 5 NovŠumperk 14:48No data—
Wed 4 NovŠumperk 14:49No data—
Tue 3 NovŠumperk 14:48No data—
Mon 2 NovŠumperk 14:48No data—
Fri 30 OctŠumperk 14:48No data—
Thu 29 OctŠumperk 14:48No data—
Tue 27 OctŠumperk 14:48No data—
Mon 26 OctŠumperk 14:48No data—
Fri 23 OctŠumperk 14:48No data—
Thu 22 OctŠumperk 14:48No data—
Wed 21 OctŠumperk 14:48No data—
Tue 20 OctŠumperk 14:48No data—
Mon 19 OctŠumperk 14:48No data—
Fri 16 OctŠumperk 14:48No data—
Thu 15 OctŠumperk 14:48No data—
Wed 14 OctŠumperk 14:48No data—
Tue 13 OctŠumperk 14:48No data—
Mon 12 OctŠumperk 14:48No data—
Fri 9 OctŠumperk 14:48No data—
Thu 8 OctŠumperk 14:48No data—
Wed 7 OctŠumperk 14:48No data—
Tue 6 OctŠumperk 14:48No data—
Mon 5 Oct— 15:13+3 min+5 min