Os 3851 3851 Přerov – Olomouc hl. n.

View line Os 3851

Přerov 04:59 → Olomouc hl. n. 05:17 Daily 0 h 18 min · 5 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Olomouc hl. n. at 05:19 No data

  1. Přerov04:59
  2. Rokytnice u Přerova05:03
  3. Brodek u Přerova05:07
  4. Grygov05:11
  5. Olomouc hl. n.05:17

Next service: tomorrow 04:59 from Přerov · Sun 15 Nov

Next departure 04:59 tomorrow · Přerov
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
80%
40/50 runs under 3 min
RT coverage: 50 full · 0 partial · 40 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 Olomouc hl. n., 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 25 Sept Max en route +30 min · last fix heading to — +22 min
  • Mon 5 Oct Max en route +19 min · last fix heading to — +19 min
  • Tue 29 Sept Max en route +10 min · last fix heading to — +8 min
  • Tue 15 Sept Max en route +11 min · last fix heading to — +8 min
  • Sat 22 Aug Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 40
  • 3–10 min 16% · 8
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 50 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:59on time on time
05:03 / 05:04≈ on time ≈ +1 min
05:07≈ on time ≈ +2 min
05:11 / 05:12≈ on time ≈ +3 min
05:17on 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
Sat 14 NovOlomouc hl. n. 05:19No data—
Fri 13 NovŠumperk 06:34No data—
Thu 12 NovŠumperk 06:34No data—
Wed 11 NovŠumperk 06:34No data—
Tue 10 NovŠumperk 06:34No data—
Mon 9 NovŠumperk 06:34No data—
Sun 8 NovOlomouc hl. n. 05:18No data—
Sat 7 NovOlomouc hl. n. 05:18No data—
Fri 6 NovŠumperk 06:34No data—
Thu 5 NovŠumperk 06:34No data—
Wed 4 NovŠumperk 06:34No data—
Tue 3 NovŠumperk 06:34No data—
Mon 2 NovŠumperk 06:34No data—
Sun 1 NovOlomouc hl. n. 05:18No data—
Sat 31 OctOlomouc hl. n. 05:18No data—
Fri 30 OctŠumperk 06:36No data—
Thu 29 OctŠumperk 06:36No data—
Wed 28 OctOlomouc hl. n. 05:19No data—
Tue 27 OctŠumperk 06:36No data—
Mon 26 OctŠumperk 06:36No data—
Sun 25 OctOlomouc hl. n. 05:18No data—
Sat 24 OctOlomouc hl. n. 05:18No data—
Fri 23 OctŠumperk 06:36No data—
Thu 22 OctŠumperk 06:36No data—
Wed 21 OctŠumperk 06:36No data—
Tue 20 OctŠumperk 06:36No data—
Mon 19 OctŠumperk 06:36No data—
Sun 18 OctOlomouc hl. n. 05:18No data—
Sat 17 OctOlomouc hl. n. 05:18No data—
Fri 16 OctŠumperk 06:36No data—