Os 3835 3835 Vyškov na Moravě – Šumperk

View line Os 3835

Vyškov na Moravě 15:04 → Šumperk 17:35 Daily 2 h 31 min · 31 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Sunday 8 November No data

Next service: today 15:04 from Vyškov na Moravě · Mon 9 Nov

Next departure 15:04 today · Vyškov na Moravě
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
96%
53/55 runs under 3 min
RT coverage: 55 full · 0 partial · 34 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

Worst days

  • Tue 15 Sept Max en route +12 min · last fix heading to — +7 min
  • Sun 27 Sept Max en route +7 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 53
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 86% T n=7
  • 100% W n=8
  • 100% T n=8
  • 100% F n=8
  • 100% S n=8
  • 88% S n=8

Stops and timetable

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

Last 90 days, 55 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
15:04on time +3 min
15:09≈ on time ≈ +3 min
15:13 / 15:15≈ on time ≈ +3 min
15:18≈ on time ≈ +3 min
15:22 / 15:25≈ on time ≈ +3 min
15:29 / 15:30≈ on time ≈ +3 min
15:33≈ on time ≈ +3 min
15:37 / 15:38≈ on time ≈ +3 min
15:42≈ on time ≈ +3 min
15:47 / 15:50≈ on time ≈ +3 min
15:56 / 16:00≈ on time ≈ +3 min
16:04 / 16:05≈ on time ≈ +3 min
16:08≈ on time ≈ +3 min
16:12 / 16:13≈ on time ≈ +3 min
16:18 / 16:32≈ on time ≈ +3 min
16:36≈ on time ≈ +2 min
16:39 / 16:40≈ on time ≈ +2 min
16:43≈ on time ≈ +2 min
16:47 / 16:49≈ on time ≈ +2 min
16:51 / 16:52≈ on time ≈ +1 min
16:55≈ on time ≈ +1 min
16:58 / 16:59≈ on time ≈ +1 min
17:02≈ on time ≈ +1 min
17:05 / 17:06≈ on time ≈ +1 min
17:10≈ on time ≈ +1 min
17:12≈ on time ≈ +1 min
17:14≈ on time ≈ +1 min
17:20≈ on time ≈ +1 min
17:24≈ on time ≈ +1 min
17:29≈ on time ≈ +1 min
17:35on 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
Sun 8 NovŠumperk 17:34No data—
Sat 7 NovŠumperk 17:34No data—
Fri 6 NovUničov 17:04No data—
Thu 5 NovUničov 17:04No data—
Wed 4 NovUničov 17:04No data—
Tue 3 NovUničov 17:04No data—
Mon 2 NovUničov 17:04No data—
Sun 1 NovŠumperk 17:36No data—
Sat 31 OctŠumperk 17:36No data—
Fri 30 OctUničov 17:06No data—
Thu 29 OctUničov 17:06No data—
Wed 28 OctŠumperk 17:36No data—
Tue 27 OctUničov 17:07No data—
Mon 26 OctUničov 17:06No data—
Sun 25 OctŠumperk 17:36No data—
Sat 24 OctŠumperk 17:36No data—
Fri 23 OctUničov 17:06No data—
Thu 22 OctUničov 17:06No data—
Wed 21 OctUničov 17:06No data—
Tue 20 OctUničov 17:06No data—
Mon 19 OctUničov 17:06No data—
Sun 18 OctŠumperk 17:36No data—
Sat 17 OctŠumperk 17:36No data—
Fri 16 OctUničov 17:06No data—
Thu 15 OctUničov 17:06No data—
Wed 14 OctUničov 17:06No data—
Tue 13 OctUničov 17:06No data—
Mon 12 OctUničov 17:06No data—
Sun 11 OctŠumperk 17:36No data—
Sat 10 OctŠumperk 17:36No data—