Os 3829 3829 Vyškov na Moravě – Uničov

View line Os 3829

Vyškov na Moravě 13:04 → Uničov 15:05 Daily 2 h 01 min · 24 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Uničov at 15:04 No data

  1. Vyškov na Moravě13:04
  2. Nezamyslice13:22
  3. Chropyně13:42
  4. Brodek u Přerova14:11
  5. Hlušovice14:36
  6. Babice u Šternberka14:51
  7. Uničov15:05

Next service: tomorrow 13:04 from Vyškov na Moravě · Sat 21 Nov

Next departure 13:04 tomorrow · Vyškov na Moravě
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
95%
42/44 runs under 3 min
RT coverage: 44 full · 0 partial · 46 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 Uničov, 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 22 Sept Max en route +18 min · last fix heading to — +6 min
  • Tue 15 Sept Max en route +6 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 42
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 67% T n=6
  • 100% W n=6
  • 100% T n=6
  • 100% F n=6
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

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