Sp 13002 13002 Olomouc hl. n. – Šumperk

View line Sp 13002

Olomouc hl. n. 06:00 → Šumperk 06:48 Mon, Tue, Wed, Thu, Fri 0 h 48 min · 12 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 06:00 from Olomouc hl. n. · Mon 9 Nov

Next departure 06:00 Monday · Olomouc hl. n.
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
95%
38/40 runs under 3 min
RT coverage: 40 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
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 2 Sept Max en route +24 min · last fix heading to — +23 min
  • Wed 23 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 38
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 75% W n=8
  • 100% T n=8
  • 100% 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.

StopSched.Usually 9 days in 10
06:00on time +3 min
06:05≈ on time ≈ +3 min
06:07≈ on time ≈ +3 min
06:10 / 06:11≈ on time ≈ +3 min
06:17≈ on time ≈ +3 min
06:18 / 06:19≈ on time ≈ +3 min
06:23≈ on time ≈ +2 min
06:26 / 06:28≈ on time ≈ +2 min
06:30 / 06:31≈ on time ≈ +2 min
06:35 / 06:40≈ on time ≈ +2 min
06:42 / 06:43≈ on time ≈ +2 min
06:48on 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

DateLast stopFinalMax
Fri 6 NovŠumperk 06:49No data—
Thu 5 NovŠumperk 06:49No data—
Wed 4 NovŠumperk 06:49No data—
Tue 3 NovŠumperk 06:49No data—
Mon 2 NovŠumperk 06:49No data—
Fri 30 OctŠumperk 06:49No data—
Thu 29 OctŠumperk 06:49No data—
Tue 27 OctŠumperk 06:49No data—
Mon 26 OctŠumperk 06:49No data—
Fri 23 OctŠumperk 06:49No data—
Thu 22 OctŠumperk 06:49No data—
Wed 21 OctŠumperk 06:49No data—
Tue 20 OctŠumperk 06:49No data—
Mon 19 OctŠumperk 06:49No data—
Fri 16 OctŠumperk 06:49No data—
Thu 15 OctŠumperk 06:49No data—
Wed 14 OctŠumperk 06:49No data—
Tue 13 OctŠumperk 06:49No data—
Mon 12 OctŠumperk 06:49No data—
Fri 9 OctŠumperk 06:49No data—
Thu 8 OctŠumperk 06:49No data—
Wed 7 OctŠumperk 06:49No data—
Tue 6 OctŠumperk 06:49No data—
Mon 5 Oct— 07:170 min+2 min
Fri 2 Oct— 07:19+2 min+2 min
Thu 1 Oct— 07:180 min—
Wed 30 Sept— 07:160 min+1 min
Tue 29 Sept— 07:19+2 min+3 min
Fri 25 Sept— 07:520 min+2 min
Thu 24 Sept— 07:18+2 min+3 min