Os 3652 3652 Hanušovice – Šumperk

View line Os 3652

Hanušovice 06:01 → Šumperk 06:41 Mon, Tue, Wed, Thu, Fri 0 h 40 min · 11 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 06:01 from Hanušovice · Fri 6 Nov

Next departure 06:01 today · Hanušovice
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
100%
40/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 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

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

  • Early 3% · 1
  • On time 98% · 39
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 100% 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 (11 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:01on time on time
06:03≈ on time ≈ on time
06:06≈ on time ≈ on time
06:08 / 06:09≈ on time ≈ on time
06:12≈ on time ≈ +1 min
06:15 / 06:16≈ on time ≈ +1 min
06:19≈ on time ≈ +1 min
06:22≈ on time ≈ +1 min
06:25≈ on time ≈ +1 min
06:29 / 06:35≈ on time ≈ +1 min
06:41on 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
Thu 5 NovŠumperk 06:42No data—
Wed 4 NovŠumperk 06:42No data—
Tue 3 NovŠumperk 06:42No data—
Mon 2 NovŠumperk 06:42No data—
Fri 30 OctŠumperk 06:42No data—
Thu 29 OctŠumperk 06:42No data—
Tue 27 OctŠumperk 06:42No data—
Mon 26 OctŠumperk 06:42No data—
Fri 23 OctŠumperk 06:42No data—
Thu 22 OctŠumperk 06:42No data—
Wed 21 OctŠumperk 06:42No data—
Tue 20 OctŠumperk 06:42No data—
Mon 19 OctŠumperk 06:42No data—
Fri 16 OctŠumperk 06:42No data—
Thu 15 OctŠumperk 06:42No data—
Wed 14 OctŠumperk 06:42No data—
Tue 13 OctŠumperk 06:42No data—
Mon 12 OctŠumperk 06:42No data—
Fri 9 OctŠumperk 06:42No data—
Thu 8 OctŠumperk 06:42No data—
Wed 7 OctŠumperk 06:42No data—
Tue 6 OctŠumperk 06:42No data—
Mon 5 Oct— 06:58+2 min+2 min
Fri 2 Oct— 06:57+1 min+1 min
Thu 1 Oct— 06:560 min—
Wed 30 Sept— 06:550 min—
Tue 29 Sept— 06:550 min+3 min
Fri 25 Sept— 06:550 min—
Thu 24 Sept— 06:550 min—
Wed 23 Sept— 06:57+2 min+2 min