Os 14242 14242 Vizovice – Otrokovice

View line Os 14242

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

It has not run yet today

Last recorded run: Monday 9 November No data

Next service: today 16:52 from Vizovice · Tue 10 Nov

Next departure 16:52 today · Vizovice
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
90%
44/49 runs under 3 min
RT coverage: 49 full · 0 partial · 36 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 +6 min · last fix heading to — +4 min
  • Fri 18 Sept Max en route +4 min · last fix heading to — +4 min
  • Thu 20 Aug Max en route +4 min · last fix heading to — +4 min
  • Fri 25 Sept Max en route +3 min · last fix heading to — +3 min
  • Fri 28 Aug Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 44
  • 3–10 min 10% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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