Os 3536 3536 Hlubočky – Olomouc hl. n.

View line Os 3536

Hlubočky 06:04 → Olomouc hl. n. 06:24 Mon, Tue, Wed, Thu, Fri 0 h 20 min · 7 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Friday 13 November No data

Next service: today 06:04 from Hlubočky · Mon 16 Nov

Next departure 06:04 today · Hlubočky
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
79%
26/33 runs under 3 min
RT coverage: 33 full · 0 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
P90
+5min
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 +7 min · last fix heading to — +7 min
  • Thu 1 Oct Max en route +6 min · last fix heading to — +6 min
  • Wed 30 Sept Max en route +6 min · last fix heading to — +6 min
  • Fri 2 Oct Max en route +5 min · last fix heading to — +5 min
  • Wed 23 Sept Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 26
  • 3–10 min 21% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 50% T n=6
  • 71% W n=7
  • 86% T n=7
  • 86% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

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