Os 3201 3201 Přerov – Vsetín

View line Os 3201

Přerov 04:28 → Vsetín 05:46 Daily 1 h 18 min · 18 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Vsetín at 05:47 No data

  1. Přerov04:28
  2. Lipník nad Bečvou04:39
  3. Hranice na Moravě město05:00
  4. Špičky05:09
  5. Hustopeče nad Bečvou05:13
  6. Brňov05:32
  7. Vsetín05:46

Next service: tomorrow 04:28 from Přerov · Sat 7 Nov

Next departure 04:28 tomorrow · Přerov
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
88%
51/58 runs under 3 min
RT coverage: 58 full · 0 partial · 32 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
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 2 Oct Max en route +19 min · last fix heading to — +11 min
  • Thu 17 Sept Max en route +8 min · last fix heading to — +6 min
  • Mon 17 Aug Max en route +8 min · last fix heading to — +6 min
  • Sat 12 Sept Max en route +5 min · last fix heading to — +5 min
  • Fri 21 Aug Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 51
  • 3–10 min 10% · 6
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 78% M n=9
  • 88% T n=8
  • 100% W n=8
  • 88% T n=8
  • 75% F n=8
  • 88% S n=8
  • 100% S n=9

Stops and timetable

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

Last 90 days, 58 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
04:28on time on time
04:33≈ on time ≈ on time
04:36≈ on time ≈ on time
04:39 / 04:40≈ on time ≈ +1 min
04:48≈ on time ≈ +1 min
04:53 / 04:55≈ on time ≈ +1 min
05:00≈ on time ≈ +1 min
05:03≈ on time ≈ +1 min
05:06≈ on time ≈ +2 min
05:09≈ on time ≈ +2 min
05:11≈ on time ≈ +2 min
05:13 / 05:14≈ on time ≈ +2 min
05:18≈ on time ≈ +2 min
05:22 / 05:28≈ on time ≈ +2 min
05:32≈ on time ≈ +3 min
05:35≈ on time ≈ +3 min
05:40≈ on time ≈ +3 min
05:46on time +3 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 NovVsetín 05:47No data—
Thu 5 NovVsetín 05:47No data—
Wed 4 NovVsetín 05:47No data—
Tue 3 NovVsetín 05:48No data—
Mon 2 NovVsetín 05:47No data—
Sun 1 NovVsetín 05:47No data—
Sat 31 OctVsetín 05:47No data—
Fri 30 OctVsetín 05:47No data—
Thu 29 OctVsetín 05:47No data—
Wed 28 OctVsetín 05:48No data—
Tue 27 OctVsetín 05:47No data—
Mon 26 OctVsetín 05:47No data—
Sun 25 OctVsetín 05:47No data—
Sat 24 OctVsetín 05:47No data—
Fri 23 OctVsetín 05:47No data—
Thu 22 OctVsetín 05:47No data—
Wed 21 OctVsetín 05:47No data—
Tue 20 OctVsetín 05:47No data—
Mon 19 OctVsetín 05:47No data—
Sun 18 OctVsetín 05:47No data—
Sat 17 OctVsetín 05:47No data—
Fri 16 OctVsetín 05:47No data—
Thu 15 OctVsetín 05:47No data—
Wed 14 OctVsetín 05:47No data—
Tue 13 OctVsetín 05:47No data—
Mon 12 OctVsetín 05:47No data—
Sun 11 OctVsetín 05:47No data—
Sat 10 OctVsetín 05:47No data—
Fri 9 OctVsetín 05:47No data—
Thu 8 OctVsetín 05:47No data—