Os 13064 13064 Šumperk – Sobotín

View line Os 13064

Šumperk 09:56 → Sobotín 10:16 Sat, Sun 0 h 20 min · 7 stops České dráhy, a.s.

It does not run today

Last recorded run: Sunday 1 November No data

Next service: tomorrow 09:56 from Šumperk · Sat 7 Nov

Next departure 09:56 tomorrow · Šumperk
On-time · 30 days
—
Too little data (0/9 runs with data)
RT coverage: 0 full · 0 partial · 9 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 18 full · 0 partial · 9 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 Sobotín, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 29 Aug Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 17
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 88% S n=8
  • 100% S n=9

Stops and timetable

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

Last 90 days, 18 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
09:56on time +2 min
09:59≈ on time ≈ +2 min
10:01≈ on time ≈ +2 min
10:04≈ on time ≈ +2 min
10:07 / 10:10≈ on time ≈ +2 min
10:12≈ on time ≈ +2 min
10:16on 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
Sun 1 NovSobotín 10:17No data—
Sat 31 OctSobotín 10:17No data—
Wed 28 OctSobotín 10:17No data—
Sun 25 OctSobotín 10:17No data—
Sat 24 OctSobotín 10:17No data—
Sun 18 OctSobotín 10:17No data—
Sat 17 OctSobotín 10:17No data—
Sun 11 OctSobotín 10:17No data—
Sat 10 OctSobotín 10:17No data—
Sun 4 Oct— 10:580 min—
Sat 3 Oct— 10:570 min—
Mon 28 Sept— 10:570 min—
Sun 27 Sept— 10:570 min—
Sat 26 Sept— 10:580 min—
Sun 20 Sept— 10:570 min—
Sat 19 Sept— 10:590 min—
Sun 13 Sept— 10:570 min—
Sat 12 Sept— 10:580 min—
Sun 6 Sept— 10:580 min—
Sat 5 Sept— 11:00+2 min+2 min
Sun 30 Aug— 10:580 min—
Sat 29 Aug— 11:04+6 min+6 min
Sun 23 Aug— 10:580 min—
Sat 22 Aug— 10:580 min—
Sun 16 Aug— 10:570 min—
Sat 15 Aug— 10:59+2 min+2 min
Sun 9 Aug— 10:58+1 min+1 min