Os 3658 3658 Hanušovice – Šumperk

View line Os 3658

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

✓ Today’s run finished

Today, last fix heading to Šumperk at 12:45 No data

  1. Hanušovice12:04
  2. Raškov12:09
  3. Bohdíkov12:11
  4. Ruda nad Moravou12:18
  5. Bohutín12:25
  6. Bludov lázně12:28
  7. Šumperk12:43

Next service: tomorrow 12:04 from Hanušovice · Fri 6 Nov

Next departure 12: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
78%
46/59 runs under 3 min
RT coverage: 59 full · 0 partial · 31 no data
Typical delay
0min
Median at arrival, 90 days
P90
+6min
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

  • Fri 4 Sept Max en route +14 min · last fix heading to — +11 min
  • Mon 5 Oct Max en route +9 min · last fix heading to — +9 min
  • Sat 29 Aug Max en route +13 min · last fix heading to — +8 min
  • Mon 28 Sept Max en route +9 min · last fix heading to — +7 min
  • Mon 21 Sept Max en route +7 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 24% · 14
  • On time 54% · 32
  • 3–10 min 20% · 12
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=9
  • 88% T n=8
  • 75% W n=8
  • 88% T n=8
  • 63% F n=8
  • 67% S n=9
  • 100% S n=9

Stops and timetable

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

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