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

View line Os 13032

Zábřeh na Moravě 23:37 → Šumperk 23:53 Daily 0 h 16 min · 5 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Wednesday 18 November No data

Next service: today 23:37 from Zábřeh na Moravě · Thu 19 Nov

Next departure 23:37 today · Zábřeh na Moravě
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
62%
26/42 runs under 3 min
RT coverage: 42 full · 0 partial · 45 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+10min
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

  • Sun 23 Aug Max en route +21 min · last fix heading to — +18 min
  • Tue 1 Sept Max en route +16 min · last fix heading to — +14 min
  • Thu 3 Sept Max en route +14 min · last fix heading to — +13 min
  • Fri 18 Sept Max en route +13 min · last fix heading to — +10 min
  • Sun 6 Sept Max en route +12 min · last fix heading to — +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 62% · 26
  • 3–10 min 26% · 11
  • 10–30 min 12% · 5
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 67% T n=6
  • 50% W n=6
  • 60% T n=5
  • 67% F n=6
  • 33% S n=6
  • 57% S n=7

Stops and timetable

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

Last 90 days, 42 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
23:37+4 min +14 min
23:39 / 23:40≈ +3 min ≈ +14 min
23:44≈ +3 min ≈ +13 min
23:47 / 23:48≈ +2 min ≈ +11 min
23:53+1 min +10 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
Wed 18 NovŠumperk 23:54No data—
Tue 17 NovŠumperk 23:54No data—
Mon 16 NovŠumperk 23:55No data—
Sun 15 NovŠumperk 23:54No data—
Sat 14 NovŠumperk 23:54No data—
Fri 13 NovŠumperk 23:54No data—
Thu 12 NovŠumperk 23:54No data—
Wed 11 NovŠumperk 23:54No data—
Tue 10 NovŠumperk 23:54No data—
Mon 9 NovŠumperk 23:54No data—
Sun 8 NovŠumperk 23:55No data—
Sat 7 NovŠumperk 23:54No data—
Fri 6 NovŠumperk 23:54No data—
Thu 5 NovŠumperk 23:54No data—
Wed 4 NovŠumperk 23:54No data—
Tue 3 NovŠumperk 23:54No data—
Mon 2 NovŠumperk 23:54No data—
Sun 1 NovŠumperk 23:54No data—
Sat 31 OctŠumperk 23:54No data—
Fri 30 OctŠumperk 23:54No data—
Thu 29 OctŠumperk 23:54No data—
Wed 28 OctŠumperk 23:54No data—
Tue 27 OctŠumperk 23:55No data—
Mon 26 OctŠumperk 23:54No data—
Sun 25 OctŠumperk 23:54No data—
Sat 24 OctŠumperk 23:54No data—
Fri 23 OctŠumperk 23:54No data—
Thu 22 OctŠumperk 23:54No data—
Wed 21 OctŠumperk 23:54No data—
Tue 20 OctŠumperk 23:54No data—