Os 14234 14234 Vizovice – Otrokovice

View line Os 14234

Vizovice 14:52 → Otrokovice 15:38 Daily 0 h 46 min · 15 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Otrokovice at 15:39 No data

  1. Vizovice14:52
  2. Lípa nad Dřevnicí15:01
  3. Zlín-Podvesná15:10
  4. Zlín střed15:15
  5. Zlín-Louky15:24
  6. Zlín-Malenovice zastávka15:33
  7. Otrokovice15:38

Next service: tomorrow 14:52 from Vizovice · Thu 12 Nov

Next departure 14:52 tomorrow · Vizovice
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
92%
46/50 runs under 3 min
RT coverage: 50 full · 0 partial · 37 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Otrokovice, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 4 Oct Max en route +5 min · last fix heading to — +5 min
  • Wed 19 Aug Max en route +5 min · last fix heading to — +5 min
  • Sun 13 Sept Max en route +4 min · last fix heading to — +4 min
  • Mon 17 Aug Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 46
  • 3–10 min 8% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 100% T n=7
  • 86% W n=7
  • 100% T n=7
  • 100% F n=7
  • 100% S n=7
  • 71% S n=7

Stops and timetable

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

Last 90 days, 50 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
14:52on time on time
14:56≈ on time ≈ on time
15:01≈ on time ≈ on time
15:04≈ on time ≈ +1 min
15:07≈ on time ≈ +1 min
15:10≈ on time ≈ +1 min
15:13≈ on time ≈ +1 min
15:15 / 15:20≈ on time ≈ +1 min
15:22≈ on time ≈ +1 min
15:24≈ on time ≈ +1 min
15:27 / 15:29≈ on time ≈ +2 min
15:31≈ on time ≈ +2 min
15:33≈ on time ≈ +2 min
15:36≈ on time ≈ +2 min
15:38on time +2 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
Wed 11 NovOtrokovice 15:39No data—
Tue 10 NovOtrokovice 15:39No data—
Mon 9 NovOtrokovice 15:39No data—
Sun 8 NovOtrokovice 15:39No data—
Sat 7 NovOtrokovice 15:40No data—
Fri 6 NovOtrokovice 15:39No data—
Thu 5 NovOtrokovice 15:39No data—
Wed 4 NovOtrokovice 15:40No data—
Tue 3 NovOtrokovice 15:39No data—
Mon 2 NovOtrokovice 15:39No data—
Sun 1 NovOtrokovice 15:39No data—
Sat 31 OctOtrokovice 15:39No data—
Fri 30 OctOtrokovice 15:39No data—
Thu 29 OctOtrokovice 15:39No data—
Wed 28 OctOtrokovice 15:39No data—
Tue 27 OctOtrokovice 15:39No data—
Mon 26 OctOtrokovice 15:39No data—
Sun 25 OctOtrokovice 15:39No data—
Sat 24 OctOtrokovice 15:39No data—
Fri 23 OctOtrokovice 15:39No data—
Thu 22 OctOtrokovice 15:39No data—
Wed 21 OctOtrokovice 15:39No data—
Tue 20 OctOtrokovice 15:39No data—
Mon 19 OctOtrokovice 15:39No data—
Sun 18 OctOtrokovice 15:39No data—
Sat 17 OctOtrokovice 15:39No data—
Fri 16 OctOtrokovice 15:39No data—
Thu 15 OctOtrokovice 15:39No data—
Wed 14 OctOtrokovice 15:39No data—
Tue 13 OctOtrokovice 15:39No data—