Os 14200 14200 Vizovice – Otrokovice

View line Os 14200

Vizovice 03:29 → Otrokovice 04:10 Mon, Tue, Wed, Thu, Fri 0 h 41 min · 15 stops České dráhy, a.s.

✓ Today’s run finished

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

  1. Vizovice03:29
  2. Lípa nad Dřevnicí03:38
  3. Zlín-Podvesná03:48
  4. Zlín střed03:52
  5. Zlín-Louky03:58
  6. Zlín-Malenovice zastávka04:05
  7. Otrokovice04:10

Next service: tomorrow 03:29 from Vizovice · Tue 10 Nov

Next departure 03:29 tomorrow · Vizovice
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
97%
35/36 runs under 3 min
RT coverage: 36 full · 0 partial · 25 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 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

  • Tue 29 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 36 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
03:29on time on time
03:33≈ on time ≈ on time
03:38 / 03:39≈ on time ≈ on time
03:42≈ on time ≈ on time
03:45≈ on time ≈ on time
03:48≈ on time ≈ on time
03:50≈ on time ≈ on time
03:52 / 03:53≈ on time ≈ on time
03:56≈ on time ≈ on time
03:58≈ on time ≈ on time
04:01≈ on time ≈ on time
04:03≈ on time ≈ on time
04:05≈ on time ≈ on time
04:08≈ on time ≈ on time
04:10on 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 9 NovOtrokovice 04:09No data—
Fri 6 NovOtrokovice 04:09No data—
Thu 5 NovOtrokovice 04:09No data—
Wed 4 NovOtrokovice 04:09No data—
Tue 3 NovOtrokovice 04:09No data—
Mon 2 NovOtrokovice 04:09No data—
Fri 30 OctOtrokovice 04:11No data—
Thu 29 OctOtrokovice 04:11No data—
Tue 27 OctOtrokovice 04:11No data—
Mon 26 OctOtrokovice 04:11No data—
Fri 23 OctOtrokovice 04:11No data—
Thu 22 OctOtrokovice 04:09No data—
Wed 21 OctOtrokovice 04:11No data—
Tue 20 OctOtrokovice 04:11No data—
Mon 19 OctOtrokovice 04:11No data—
Fri 16 OctOtrokovice 04:11No data—
Thu 15 OctOtrokovice 04:11No data—
Wed 14 OctOtrokovice 04:11No data—
Tue 13 OctOtrokovice 04:11No data—
Mon 12 OctOtrokovice 04:11No data—
Fri 9 OctOtrokovice 04:11No data—
Thu 8 OctOtrokovice 04:11No data—
Wed 7 OctOtrokovice 04:11No data—
Tue 6 OctOtrokovice 04:11No data—
Mon 5 Oct— 04:150 min—
Fri 2 Oct— 04:150 min—
Thu 1 Oct— 04:160 min—
Wed 30 Sept— 04:17+2 min+2 min
Tue 29 Sept— 04:18+3 min+3 min
Fri 25 Sept— 04:15−1 min—