Os 3664 3664 Hanušovice – Šumperk

View line Os 3664

Hanušovice 18:04 → Šumperk 18:42 Daily 0 h 38 min · 11 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Šumperk at 18:43 No data

  1. Hanušovice18:04
  2. Raškov18:09
  3. Bohdíkov18:11
  4. Ruda nad Moravou18:18
  5. Bohutín18:25
  6. Bludov lázně18:28
  7. Šumperk18:42

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

Next departure 18:04 tomorrow · Hanušovice
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
61%
35/57 runs under 3 min
RT coverage: 57 full · 0 partial · 33 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+9min
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

  • Mon 28 Sept Max en route +45 min · last fix heading to — +42 min
  • Sat 12 Sept Max en route +18 min · last fix heading to — +13 min
  • Wed 19 Aug Max en route +12 min · last fix heading to — +12 min
  • Tue 8 Sept Max en route +10 min · last fix heading to — +10 min
  • Fri 4 Sept Max en route +11 min · last fix heading to — +10 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 60% · 34
  • 3–10 min 30% · 17
  • 10–30 min 7% · 4
  • 30+ min 2% · 1

On-time by weekday

  • 63% M n=8
  • 63% T n=8
  • 88% W n=8
  • 75% T n=8
  • 38% F n=8
  • 63% S n=8
  • 44% S n=9

Stops and timetable

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

Last 90 days, 57 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
18:04+5 min +10 min
18:06≈ +5 min ≈ +10 min
18:09≈ +4 min ≈ +10 min
18:11 / 18:12≈ +4 min ≈ +9 min
18:15≈ +4 min ≈ +9 min
18:18 / 18:19≈ +3 min ≈ +9 min
18:22≈ +3 min ≈ +8 min
18:25≈ +3 min ≈ +8 min
18:28≈ +2 min ≈ +8 min
18:32 / 18:36≈ +2 min ≈ +9 min
18:42+1 min +9 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
Fri 6 NovŠumperk 18:43No data—
Thu 5 NovŠumperk 18:43No data—
Wed 4 NovŠumperk 18:43No data—
Tue 3 NovŠumperk 18:43No data—
Mon 2 NovŠumperk 18:43No data—
Sun 1 NovŠumperk 18:43No data—
Sat 31 OctŠumperk 18:43No data—
Fri 30 OctŠumperk 18:43No data—
Thu 29 OctŠumperk 18:43No data—
Wed 28 OctŠumperk 18:43No data—
Tue 27 OctŠumperk 18:44No data—
Mon 26 OctŠumperk 18:43No data—
Sun 25 OctŠumperk 18:43No data—
Sat 24 OctŠumperk 18:43No data—
Fri 23 OctŠumperk 18:44No data—
Thu 22 OctŠumperk 18:43No data—
Wed 21 OctŠumperk 18:43No data—
Tue 20 OctŠumperk 18:44No data—
Mon 19 OctŠumperk 18:43No data—
Sun 18 OctŠumperk 18:43No data—
Sat 17 OctŠumperk 18:43No data—
Fri 16 OctŠumperk 18:43No data—
Thu 15 OctŠumperk 18:43No data—
Wed 14 OctŠumperk 18:43No data—
Tue 13 OctŠumperk 18:43No data—
Mon 12 OctŠumperk 18:44No data—
Sun 11 OctŠumperk 18:43No data—
Sat 10 OctŠumperk 18:43No data—
Fri 9 OctŠumperk 18:43No data—
Thu 8 OctŠumperk 18:43No data—