Os 13065 13065 Sobotín – Šumperk

View line Os 13065

Sobotín 11:05 → Šumperk 11:24 Sat, Sun 0 h 19 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:05 from Sobotín · Sat 7 Nov

Next departure 11:05 Saturday · Sobotín
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
+1min
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

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:05on time +1 min
11:09≈ on time ≈ +1 min
11:11 / 11:15≈ on time ≈ +1 min
11:17≈ on time ≈ +1 min
11:19≈ on time ≈ +1 min
11:21≈ on time ≈ +1 min
11:24on time +1 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 NovŠumperk 11:25No data—
Sat 31 OctŠumperk 11:25No data—
Wed 28 OctŠumperk 11:25No data—
Sun 25 OctŠumperk 11:25No data—
Sat 24 OctŠumperk 11:25No data—
Sun 18 OctŠumperk 11:25No data—
Sat 17 OctŠumperk 11:25No data—
Sun 11 OctŠumperk 11:25No data—
Sat 10 OctŠumperk 11:25No data—
Sun 4 Oct— 11:390 min—
Sat 3 Oct— 11:37−1 min—
Mon 28 Sept— 11:380 min—
Sun 27 Sept— 11:390 min—
Sat 26 Sept— 11:390 min—
Sun 20 Sept— 11:40+2 min+2 min
Sat 19 Sept— 11:390 min—
Sun 13 Sept— 11:380 min—
Sat 12 Sept— 11:390 min—
Sun 6 Sept— 11:380 min—
Sat 5 Sept— 11:390 min—
Sun 30 Aug— 11:39+1 min+1 min
Sat 29 Aug— 11:40+1 min+1 min
Sun 23 Aug— 11:380 min—
Sat 22 Aug— 11:380 min—
Sun 16 Aug— 11:380 min—
Sat 15 Aug— 11:380 min—
Sun 9 Aug— 11:380 min—
Sat 8 Aug— 11:37−1 min—