Os 14362 14362 Valašské Meziříčí → Vsetín

View line Os 14362

Valašské Meziříčí 16:01 → Vsetín 16:17 Mon, Tue, Wed, Thu, Fri 0 h 16 min · 5 stops ARRIVA vlaky s.r.o.

It does not run today

Last recorded run: Friday 20 November No data

Next service: Monday 16:01 from Valašské Meziříčí · Mon 23 Nov

Next departure 16:01 Monday · Valašské Meziříčí
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 32 no data
Typical delay
−1min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Vsetín, in minutes. One bar per run.

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

Worst days

  • Fri 11 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 93% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 83% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 30 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:01on time on time
16:05≈ on time ≈ on time
16:07≈ on time ≈ on time
16:11≈ 1 min early ≈ on time
16:171 min early 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
Fri 20 NovVsetín 16:18No data—
Thu 19 NovVsetín 16:18No data—
Wed 18 NovVsetín 16:18No data—
Mon 16 NovVsetín 16:18No data—
Fri 13 NovVsetín 16:18No data—
Thu 12 NovVsetín 16:18No data—
Wed 11 NovVsetín 16:18No data—
Tue 10 NovVsetín 16:18No data—
Mon 9 NovVsetín 16:18No data—
Fri 6 NovVsetín 16:18No data—
Thu 5 NovVsetín 16:18No data—
Wed 4 NovVsetín 16:18No data—
Tue 3 NovVsetín 16:18No data—
Mon 2 NovVsetín 16:18No data—
Fri 30 OctVsetín 16:18No data—
Thu 29 OctVsetín 16:18No data—
Tue 27 OctVsetín 16:19No data—
Mon 26 OctVsetín 16:18No data—
Fri 23 OctVsetín 16:18No data—
Thu 22 OctVsetín 16:18No data—
Wed 21 OctVsetín 16:18No data—
Tue 20 OctVsetín 16:18No data—
Mon 19 OctVsetín 16:18No data—
Fri 16 OctVsetín 16:18No data—
Thu 15 OctVsetín 16:18No data—
Wed 14 OctVsetín 16:18No data—
Tue 13 OctVsetín 16:18No data—
Mon 12 OctVsetín 16:18No data—
Fri 9 OctVsetín 16:18No data—
Thu 8 OctVsetín 16:18No data—