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

View line Os 13700

Uničov 04:15 → Olomouc hl. n. 04:47 Mon, Tue, Wed, Thu, Fri 0 h 32 min · 10 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Olomouc hl. n. at 04:48 No data

  1. Uničov04:15
  2. Újezd u Uničova04:20
  3. Mladějovice04:24
  4. Šternberk04:31
  5. Štarnov04:35
  6. Hlušovice04:42
  7. Olomouc hl. n.04:47

Next service: tomorrow 04:15 from Uničov · Wed 11 Nov

Next departure 04:15 tomorrow · Uničov
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
100%
37/37 runs under 3 min
RT coverage: 37 full · 0 partial · 25 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 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 37 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:15on time on time
04:17≈ on time ≈ on time
04:20 / 04:21≈ on time ≈ on time
04:24≈ on time ≈ on time
04:27 / 04:28≈ on time ≈ on time
04:31 / 04:32≈ on time ≈ on time
04:35≈ on time ≈ on time
04:38 / 04:39≈ on time ≈ on time
04:42≈ on time ≈ on time
04:47on 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
Tue 10 NovOlomouc hl. n. 04:48No data—
Mon 9 NovOlomouc hl. n. 04:48No data—
Fri 6 NovOlomouc hl. n. 04:48No data—
Thu 5 NovOlomouc hl. n. 04:48No data—
Wed 4 NovOlomouc hl. n. 04:48No data—
Tue 3 NovOlomouc hl. n. 04:49No data—
Mon 2 NovOlomouc hl. n. 04:48No data—
Fri 30 OctOlomouc hl. n. 04:48No data—
Thu 29 OctOlomouc hl. n. 04:48No data—
Tue 27 OctOlomouc hl. n. 04:48No data—
Mon 26 OctOlomouc hl. n. 04:48No data—
Fri 23 OctOlomouc hl. n. 04:48No data—
Thu 22 OctOlomouc hl. n. 04:48No data—
Wed 21 OctOlomouc hl. n. 04:48No data—
Tue 20 OctOlomouc hl. n. 04:48No data—
Mon 19 OctOlomouc hl. n. 04:48No data—
Fri 16 OctOlomouc hl. n. 04:48No data—
Thu 15 OctOlomouc hl. n. 04:48No data—
Wed 14 OctOlomouc hl. n. 04:48No data—
Tue 13 OctOlomouc hl. n. 04:48No data—
Mon 12 OctOlomouc hl. n. 04:48No data—
Fri 9 OctOlomouc hl. n. 04:48No data—
Thu 8 OctOlomouc hl. n. 04:48No data—
Wed 7 OctOlomouc hl. n. 04:48No data—
Tue 6 OctOlomouc hl. n. 04:48No data—
Mon 5 Oct— 05:01−1 min—
Fri 2 Oct— 05:010 min—
Thu 1 Oct— 05:02+1 min+2 min
Wed 30 Sept— 05:010 min—
Tue 29 Sept— 05:010 min—