Os 14212 14212 Vizovice – Otrokovice

View line Os 14212

Vizovice 07:22 → Otrokovice 08:08 Daily 0 h 46 min · 15 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Otrokovice at 08:09 No data

  1. Vizovice07:22
  2. Lípa nad Dřevnicí07:31
  3. Zlín-Podvesná07:40
  4. Zlín střed07:45
  5. Zlín-Louky07:54
  6. Zlín-Malenovice zastávka08:03
  7. Otrokovice08:08

Next service: tomorrow 07:22 from Vizovice · Fri 6 Nov

Next departure 07:22 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
70%
38/54 runs under 3 min
RT coverage: 54 full · 0 partial · 31 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+4min
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

  • Thu 3 Sept Max en route +19 min · last fix heading to — +16 min
  • Thu 24 Sept Max en route +6 min · last fix heading to — +6 min
  • Mon 17 Aug Max en route +6 min · last fix heading to — +6 min
  • Fri 28 Aug Max en route +6 min · last fix heading to — +5 min
  • Mon 5 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 70% · 38
  • 3–10 min 28% · 15
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 63% M n=8
  • 63% T n=8
  • 57% W n=7
  • 75% T n=8
  • 57% F n=7
  • 88% S n=8
  • 88% S n=8

Stops and timetable

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

Last 90 days, 54 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
07:22on time on time
07:26≈ on time ≈ on time
07:31≈ on time ≈ +1 min
07:34≈ on time ≈ +1 min
07:37≈ on time ≈ +1 min
07:40≈ on time ≈ +2 min
07:43≈ on time ≈ +2 min
07:45 / 07:50≈ +1 min ≈ +2 min
07:52≈ +1 min ≈ +3 min
07:54≈ +1 min ≈ +3 min
07:57 / 07:59≈ +1 min ≈ +3 min
08:01≈ +1 min ≈ +3 min
08:03≈ +1 min ≈ +4 min
08:06≈ +1 min ≈ +4 min
08:08+1 min +4 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
Thu 5 NovOtrokovice 08:09No data—
Wed 4 NovOtrokovice 08:09No data—
Tue 3 NovOtrokovice 08:09No data—
Mon 2 NovOtrokovice 08:09No data—
Sun 1 NovOtrokovice 08:09No data—
Sat 31 OctOtrokovice 08:09No data—
Fri 30 OctOtrokovice 08:09No data—
Thu 29 OctOtrokovice 08:09No data—
Wed 28 OctOtrokovice 08:09No data—
Tue 27 OctOtrokovice 08:09No data—
Mon 26 OctOtrokovice 08:09No data—
Sun 25 OctOtrokovice 08:09No data—
Sat 24 OctOtrokovice 08:09No data—
Fri 23 OctOtrokovice 08:09No data—
Thu 22 OctOtrokovice 08:10No data—
Wed 21 OctOtrokovice 08:09No data—
Tue 20 OctOtrokovice 08:09No data—
Mon 19 OctOtrokovice 08:09No data—
Sun 18 OctOtrokovice 08:09No data—
Sat 17 OctOtrokovice 08:09No data—
Fri 16 OctOtrokovice 08:09No data—
Thu 15 OctOtrokovice 08:09No data—
Wed 14 OctOtrokovice 08:09No data—
Tue 13 OctOtrokovice 08:09No data—
Mon 12 OctOtrokovice 08:09No data—
Sun 11 OctOtrokovice 08:09No data—
Sat 10 OctOtrokovice 08:09No data—
Fri 9 OctOtrokovice 08:09No data—
Thu 8 OctOtrokovice 08:09No data—
Wed 7 OctOtrokovice 08:09No data—