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

View line Os 13719

Olomouc hl. n. 16:55 → Uničov 17:28 Sat, Sun 0 h 33 min · 10 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Uničov at 17:29 No data

  1. Olomouc hl. n.16:55
  2. Bohuňovice17:02
  3. Štarnov17:06
  4. Babice u Šternberka17:14
  5. Mladějovice17:18
  6. Uničov zastávka17:25
  7. Uničov17:28

Next service: Saturday 16:55 from Olomouc hl. n. · Sat 14 Nov

Next departure 16:55 Saturday · Olomouc hl. n.
On-time · 30 days
—
Too little data (0/11 runs with data)
RT coverage: 0 full · 0 partial · 11 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 11 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
16:55on time +2 min
16:59≈ on time ≈ +2 min
17:02 / 17:03≈ on time ≈ +2 min
17:06≈ on time ≈ +1 min
17:10 / 17:12≈ on time ≈ +1 min
17:14 / 17:15≈ on time ≈ +1 min
17:18≈ on time ≈ +1 min
17:21 / 17:22≈ on time ≈ +1 min
17:25≈ on time ≈ on time
17:28on 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
Sun 8 NovUničov 17:29No data—
Sat 7 NovUničov 17:29No data—
Sun 1 NovUničov 17:29No data—
Sat 31 OctUničov 17:29No data—
Wed 28 OctUničov 17:29No data—
Sun 25 OctUničov 17:29No data—
Sat 24 OctUničov 17:29No data—
Sun 18 OctUničov 17:29No data—
Sat 17 OctUničov 17:29No data—
Sun 11 OctUničov 17:29No data—
Sat 10 OctUničov 17:29No data—
Sun 4 Oct— 17:430 min—
Sat 3 Oct— 17:42−1 min+3 min
Mon 28 Sept— 17:430 min—
Sun 27 Sept— 17:420 min—
Sat 26 Sept— 17:42−1 min+6 min
Sun 20 Sept— 17:41−1 min—
Sat 19 Sept— 17:42−1 min—
Sun 13 Sept— 17:41−1 min—
Sat 12 Sept— 17:430 min—
Sun 6 Sept— 17:430 min—
Sat 5 Sept— 17:44+1 min+1 min
Sun 30 Aug— 17:420 min—
Sat 29 Aug— 17:430 min—
Sun 23 Aug— 17:420 min—
Sat 22 Aug— 17:420 min+3 min
Sun 16 Aug— 17:420 min—
Sat 15 Aug— 17:420 min—