Os 3641 3641 Uničov – Šumperk

View line Os 3641

Uničov 04:28 → Šumperk 04:57 Mon, Tue, Wed, Thu, Fri 0 h 29 min · 8 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Šumperk at 04:58 No data

  1. Uničov04:28
  2. Troubelice střed04:32
  3. Troubelice zastávka04:34
  4. Libina04:42
  5. Hrabišín04:46
  6. Nový Malín04:51
  7. Šumperk04:57

Next service: tomorrow 04:28 from Uničov · Tue 10 Nov

Next departure 04:28 tomorrow · Uničov
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
97%
37/38 runs under 3 min
RT coverage: 38 full · 0 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
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

  • Wed 30 Sept Max en route +11 min · last fix heading to — +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 37
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 88% 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 (8 stops).

Last 90 days, 38 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
04:28on time on time
04:32≈ on time ≈ on time
04:34≈ on time ≈ on time
04:36≈ on time ≈ on time
04:42≈ on time ≈ +1 min
04:46≈ on time ≈ +1 min
04:51≈ on time ≈ +1 min
04:57on time on time

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
Mon 9 NovŠumperk 04:58No data—
Fri 6 NovŠumperk 04:58No data—
Thu 5 NovŠumperk 04:58No data—
Wed 4 NovŠumperk 04:58No data—
Tue 3 NovŠumperk 04:59No data—
Mon 2 NovŠumperk 04:58No data—
Fri 30 OctŠumperk 04:58No data—
Thu 29 OctŠumperk 04:58No data—
Tue 27 OctŠumperk 04:58No data—
Mon 26 OctŠumperk 04:58No data—
Fri 23 OctŠumperk 04:58No data—
Thu 22 OctŠumperk 04:58No data—
Wed 21 OctŠumperk 04:58No data—
Tue 20 OctŠumperk 04:58No data—
Mon 19 OctŠumperk 04:58No data—
Fri 16 OctŠumperk 04:58No data—
Thu 15 OctŠumperk 04:58No data—
Wed 14 OctŠumperk 04:58No data—
Tue 13 OctŠumperk 04:58No data—
Mon 12 OctŠumperk 04:58No data—
Fri 9 OctŠumperk 04:58No data—
Thu 8 OctŠumperk 04:58No data—
Wed 7 OctŠumperk 04:58No data—
Tue 6 OctŠumperk 04:58No data—
Mon 5 Oct— 05:120 min+2 min
Fri 2 Oct— 05:110 min—
Thu 1 Oct— 05:120 min+1 min
Wed 30 Sept— 05:20+9 min+11 min
Tue 29 Sept— 05:110 min+1 min
Fri 25 Sept— 05:120 min+2 min