Os 14240 14240 Vizovice – Otrokovice

View line Os 14240

Vizovice 16:22 → Otrokovice 17:08 Mon, Tue, Wed, Thu, Fri 0 h 46 min · 15 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 16:22 from Vizovice · Mon 9 Nov

Next departure 16:22 Monday · 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
89%
34/38 runs under 3 min
RT coverage: 38 full · 0 partial · 23 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

  • Mon 21 Sept Max en route +26 min · last fix heading to — +26 min
  • Wed 23 Sept Max en route +7 min · last fix heading to — +5 min
  • Mon 5 Oct Max en route +3 min · last fix heading to Otrokovice +3 min
  • Tue 18 Aug Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 34
  • 3–10 min 8% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 88% T n=8
  • 88% W n=8
  • 100% T n=8
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

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