Os 13066 13066 Šumperk – Sobotín

View line Os 13066

Šumperk 11:56 → Sobotín 12: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: Saturday 11:56 from Šumperk · Sat 7 Nov

Next departure 11:56 Saturday · Š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
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 19
  • 3–10 min 0% · 0
  • 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
  • 100% S n=9
  • 100% S n=9

Stops and timetable

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

Last 90 days, 19 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
11:56on time on time
11:59≈ on time ≈ on time
12:01≈ on time ≈ on time
12:04≈ on time ≈ on time
12:07 / 12:10≈ on time ≈ on time
12:12≈ on time ≈ on time
12:16on time on time

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 12:17No data—
Sat 31 OctSobotín 12:17No data—
Wed 28 OctSobotín 12:17No data—
Sun 25 OctSobotín 12:17No data—
Sat 24 OctSobotín 12:18No data—
Sun 18 OctSobotín 12:17No data—
Sat 17 OctSobotín 12:17No data—
Sun 11 OctSobotín 12:17No data—
Sat 10 OctSobotín 12:17No data—
Sun 4 Oct— 12:590 min—
Sat 3 Oct— 12:580 min—
Mon 28 Sept— 12:570 min—
Sun 27 Sept— 12:570 min—
Sat 26 Sept— 12:590 min—
Sun 20 Sept— 12:570 min—
Sat 19 Sept— 12:590 min—
Sun 13 Sept— 12:570 min—
Sat 12 Sept— 12:580 min—
Sun 6 Sept— 12:58+1 min+1 min
Sat 5 Sept— 12:590 min—
Sun 30 Aug— 12:58+1 min+1 min
Sat 29 Aug— 12:570 min—
Sun 23 Aug— 12:580 min—
Sat 22 Aug— 12:590 min—
Sun 16 Aug— 12:570 min—
Sat 15 Aug— 12:570 min—
Sun 9 Aug— 12:580 min—
Sat 8 Aug— 12:570 min—