Os 13704 13704 Újezd u Uničova – Olomouc hl. n.

View line Os 13704

Újezd u Uničova 06:24 → Olomouc hl. n. 06:48 Mon, Tue, Wed, Thu, Fri 0 h 24 min · 8 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Monday 16 November No data

Next service: today 06:24 from Újezd u Uničova · Wed 18 Nov

Next departure 06:24 today · Újezd u Uničova
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 31 full · 0 partial · 29 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

Worst days

  • Tue 15 Sept Max en route +19 min · last fix heading to — +16 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 30
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 32 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
06:24on time on time
06:27≈ on time ≈ on time
06:29≈ on time ≈ on time
06:32 / 06:33≈ on time ≈ on time
06:36≈ on time ≈ on time
06:39 / 06:40≈ on time ≈ +1 min
06:43≈ on time ≈ on time
06:48on 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
Mon 16 NovOlomouc hl. n. 06:49No data—
Fri 13 NovOlomouc hl. n. 06:49No data—
Thu 12 NovOlomouc hl. n. 06:49No data—
Wed 11 NovOlomouc hl. n. 06:49No data—
Tue 10 NovOlomouc hl. n. 06:49No data—
Mon 9 NovOlomouc hl. n. 06:49No data—
Fri 6 NovOlomouc hl. n. 06:49No data—
Thu 5 NovOlomouc hl. n. 06:49No data—
Wed 4 NovOlomouc hl. n. 06:49No data—
Tue 3 NovOlomouc hl. n. 06:49No data—
Mon 2 NovOlomouc hl. n. 06:49No data—
Fri 30 OctOlomouc hl. n. 06:49No data—
Thu 29 OctOlomouc hl. n. 06:49No data—
Tue 27 OctOlomouc hl. n. 06:49No data—
Mon 26 OctOlomouc hl. n. 06:49No data—
Fri 23 OctOlomouc hl. n. 06:49No data—
Thu 22 OctOlomouc hl. n. 06:49No data—
Wed 21 OctOlomouc hl. n. 06:49No data—
Tue 20 OctOlomouc hl. n. 06:49No data—
Mon 19 OctOlomouc hl. n. 06:49No data—
Fri 16 OctOlomouc hl. n. 06:49No data—
Thu 15 OctOlomouc hl. n. 06:49No data—
Wed 14 OctOlomouc hl. n. 06:49No data—
Tue 13 OctOlomouc hl. n. 06:49No data—
Mon 12 OctOlomouc hl. n. 06:49No data—
Fri 9 OctOlomouc hl. n. 06:49No data—
Thu 8 OctOlomouc hl. n. 06:49No data—
Wed 7 OctOlomouc hl. n. 06:49No data—
Tue 6 OctOlomouc hl. n. 06:49No data—
Mon 5 Oct— 07:04+1 min+2 min