Os 13701 13701 Olomouc hl. n. – Uničov

View line Os 13701

Olomouc hl. n. 04:58 → Uničov 05:34 Daily 0 h 36 min · 10 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Uničov at 05:34 No data

  1. Olomouc hl. n.04:58
  2. Bohuňovice05:05
  3. Štarnov05:09
  4. Babice u Šternberka05:20
  5. Mladějovice05:24
  6. Uničov zastávka05:31
  7. Uničov05:34

Next service: tomorrow 04:58 from Olomouc hl. n. · Fri 6 Nov

Next departure 04:58 tomorrow · Olomouc hl. n.
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
100%
59/59 runs under 3 min
RT coverage: 59 full · 0 partial · 31 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 59
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=8
  • 100% W n=8
  • 100% T n=8
  • 100% F n=8
  • 100% S n=9
  • 100% S n=9

Stops and timetable

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

Last 90 days, 59 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:58on time on time
05:02≈ on time ≈ on time
05:05 / 05:06≈ on time ≈ on time
05:09≈ on time ≈ on time
05:13 / 05:18≈ on time ≈ on time
05:20 / 05:21≈ on time ≈ on time
05:24≈ on time ≈ on time
05:27 / 05:28≈ on time ≈ on time
05:31≈ on time ≈ on time
05:34on 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
Thu 5 NovUničov 05:34No data—
Wed 4 NovUničov 05:34No data—
Tue 3 NovUničov 05:35No data—
Mon 2 NovUničov 05:34No data—
Sun 1 NovUničov 05:35No data—
Sat 31 OctUničov 05:35No data—
Fri 30 OctUničov 05:35No data—
Thu 29 OctUničov 05:35No data—
Wed 28 OctUničov 05:36No data—
Tue 27 OctUničov 05:35No data—
Mon 26 OctUničov 05:35No data—
Sun 25 OctUničov 05:35No data—
Sat 24 OctUničov 05:35No data—
Fri 23 OctUničov 05:35No data—
Thu 22 OctUničov 05:35No data—
Wed 21 OctUničov 05:35No data—
Tue 20 OctUničov 05:35No data—
Mon 19 OctUničov 05:35No data—
Sun 18 OctUničov 05:35No data—
Sat 17 OctUničov 05:35No data—
Fri 16 OctUničov 05:35No data—
Thu 15 OctUničov 05:35No data—
Wed 14 OctUničov 05:35No data—
Tue 13 OctUničov 05:35No data—
Mon 12 OctUničov 05:35No data—
Sun 11 OctUničov 05:35No data—
Sat 10 OctUničov 05:35No data—
Fri 9 OctUničov 05:35No data—
Thu 8 OctUničov 05:35No data—
Wed 7 OctUničov 05:35No data—