Os 3847 3847 Nezamyslice – Uničov

View line Os 3847

Nezamyslice 20:25 → Uničov 22:05 Daily 1 h 40 min · 20 stops České dráhy, a.s.

Running now · updated 21:27

Between Grygov and Olomouc hl. n. No data

Estimated arrival at Uničov 22:05

  1. Nezamyslice20:25
  2. Kojetín20:37
  3. Přerov20:54
  4. Grygov21:15
  5. Olomouc hl. n.21:21
  6. Štarnov21:43
  7. Uničov22:05
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
82%
47/57 runs under 3 min
RT coverage: 57 full · 0 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
P90
+4min
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

  • Wed 9 Sept Max en route +21 min · last fix heading to — +20 min
  • Sun 20 Sept Max en route +6 min · last fix heading to — +5 min
  • Fri 21 Aug Max en route +5 min · last fix heading to — +5 min
  • Thu 20 Aug Max en route +13 min · last fix heading to — +5 min
  • Sun 9 Aug Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 47
  • 3–10 min 16% · 9
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (20 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 10Today
20:25on time +3 minPassed
20:29 / 20:30≈ on time ≈ +3 minPassed
20:32 / 20:33≈ on time ≈ +3 minPassed
20:37 / 20:38≈ on time ≈ +3 minPassed
20:42≈ on time ≈ +3 minPassed
20:47 / 20:48≈ on time ≈ +3 minPassed
20:54 / 21:03≈ on time ≈ +3 minPassed
21:07 / 21:08≈ on time ≈ +2 minPassed
21:11≈ on time ≈ +2 minPassed
21:15 / 21:16≈ on time ≈ +2 minPassed
21:21 / 21:32≈ on time ≈ +2 minNext
21:36≈ on time ≈ +3 min
21:39 / 21:40≈ on time ≈ +3 min
21:43≈ on time ≈ +3 min
21:47 / 21:49≈ on time ≈ +3 min
21:51 / 21:52≈ on time ≈ +3 min
21:55≈ on time ≈ +4 min
21:58 / 21:59≈ on time ≈ +4 min
22:02≈ on time ≈ +4 min
22:05on time +4 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 NovOlomouc hl. n. 21:24Partial coverageNo data—
Thu 5 NovUničov 22:04No data—
Wed 4 NovUničov 22:04No data—
Tue 3 NovUničov 22:04No data—
Mon 2 NovUničov 22:04No data—
Sun 1 NovUničov 22:04No data—
Sat 31 OctUničov 22:06No data—
Fri 30 OctUničov 22:06No data—
Thu 29 OctUničov 22:06No data—
Wed 28 OctUničov 22:06No data—
Tue 27 OctUničov 22:07No data—
Mon 26 OctUničov 22:06No data—
Sun 25 OctUničov 22:06No data—
Sat 24 OctUničov 22:06No data—
Fri 23 OctUničov 22:06No data—
Thu 22 OctUničov 22:06No data—
Wed 21 OctUničov 22:06No data—
Tue 20 OctUničov 22:06No data—
Mon 19 OctUničov 22:07No data—
Sun 18 OctUničov 22:06No data—
Sat 17 OctUničov 22:06No data—
Fri 16 OctUničov 22:06No data—
Thu 15 OctUničov 22:06No data—
Wed 14 OctUničov 22:06No data—
Tue 13 OctUničov 22:06No data—
Mon 12 OctUničov 22:06No data—
Sun 11 OctUničov 22:06No data—
Sat 10 OctUničov 22:06No data—
Fri 9 OctUničov 22:06No data—
Thu 8 OctUničov 22:07No data—