Os 3614 3614 Hanušovice – Šumperk

View line Os 3614

Hanušovice 04:41 → Šumperk 05:23 Sat, Sun 0 h 42 min · 11 stops České dráhy, a.s.

It does not run today

Last recorded run: Sunday 1 November No data

Next service: tomorrow 04:41 from Hanušovice · Sat 7 Nov

Next departure 04:41 tomorrow · Hanušovice
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
−1min
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

Worst days

  • Sun 27 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 6% · 1
  • On time 89% · 16
  • 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
  • 100% S n=8
  • 89% S n=9

Stops and timetable

Timetable of the latest run from the operator’s GTFS (11 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
Hanušovice
04:41on time on time
Hanušovice Holba
04:43≈ on time ≈ on time
Raškov
04:46≈ on time ≈ on time
Bohdíkov
04:49≈ on time ≈ on time
Komňátka
04:52≈ on time ≈ +1 min
Ruda nad Moravou
04:55 / 04:56≈ on time ≈ +1 min
Bartoňov
04:59≈ on time ≈ +1 min
Bohutín
05:02≈ on time ≈ +1 min
Bludov lázně
05:05≈ 1 min early ≈ +1 min
Bludov
05:10 / 05:17≈ 1 min early ≈ +1 min
Šumperk
05:231 min early +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 05:24No data—
Sat 31 OctŠumperk 05:24No data—
Wed 28 OctŠumperk 05:25No data—
Sun 25 OctŠumperk 05:24No data—
Sat 24 OctŠumperk 05:24No data—
Sun 18 OctŠumperk 05:24No data—
Sat 17 OctŠumperk 05:24No data—
Sun 11 OctŠumperk 05:24No data—
Sat 10 OctŠumperk 05:24No data—
Sun 4 Oct— 05:370 min—
Sat 3 Oct— 05:370 min—
Mon 28 Sept— 05:370 min+3 min
Sun 27 Sept— 05:40+3 min+3 min
Sat 26 Sept— 05:38+2 min+2 min
Sun 20 Sept— 05:35−2 min—
Sat 19 Sept— 05:37−1 min—
Sun 13 Sept— 05:36−1 min—
Sat 12 Sept— 05:37−1 min+1 min
Sun 6 Sept— 05:370 min—
Sat 5 Sept— 05:380 min—
Sun 30 Aug— 05:36−1 min—
Sat 29 Aug— 05:38+1 min+2 min
Sun 23 Aug— 05:36−1 min—
Sat 22 Aug— 05:36−1 min—
Sun 16 Aug— 05:36−1 min—
Sat 15 Aug— 05:36−1 min—
Sun 9 Aug— 05:36−1 min+2 min