Os 3215 3215 Přerov – Vsetín

View line Os 3215

Přerov 10:27 → Vsetín 11:55 Daily 1 h 28 min · 18 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Vsetín at 11:54 No data

  1. Přerov10:27
  2. Lipník nad Bečvou10:38
  3. Hranice na Moravě město11:07
  4. Špičky11:16
  5. Hustopeče nad Bečvou11:21
  6. Brňov11:41
  7. Vsetín11:55

Next service: tomorrow 10:27 from Přerov · Sun 15 Nov

Next departure 10:27 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
80%
40/50 runs under 3 min
RT coverage: 50 full · 0 partial · 40 no data
Typical delay
0min
Median at arrival, 90 days
P90
+5min
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

  • Sat 22 Aug Max en route +13 min · last fix heading to — +13 min
  • Mon 5 Oct Max en route +14 min · last fix heading to — +11 min
  • Wed 2 Sept Max en route +11 min · last fix heading to — +9 min
  • Mon 14 Sept Max en route +8 min · last fix heading to — +8 min
  • Thu 20 Aug Max en route +12 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 32% · 16
  • On time 48% · 24
  • 3–10 min 16% · 8
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 71% T n=7
  • 86% W n=7
  • 71% T n=7
  • 86% F n=7
  • 86% S n=7
  • 86% S n=7

Stops and timetable

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

Last 90 days, 50 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
10:27on time +6 min
10:32≈ on time ≈ +6 min
10:35≈ on time ≈ +6 min
10:38 / 10:39≈ on time ≈ +6 min
10:47≈ on time ≈ +6 min
10:52 / 11:02≈ on time ≈ +6 min
11:07≈ on time ≈ +5 min
11:10≈ on time ≈ +5 min
11:13≈ on time ≈ +5 min
11:16≈ on time ≈ +5 min
11:18 / 11:19≈ on time ≈ +5 min
11:21≈ on time ≈ +5 min
11:25 / 11:26≈ on time ≈ +5 min
11:29 / 11:37≈ on time ≈ +5 min
11:41≈ on time ≈ +5 min
11:44≈ on time ≈ +5 min
11:49≈ on time ≈ +5 min
11:55on time +5 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
Sat 14 NovVsetín 11:54No data—
Fri 13 NovVsetín 11:54No data—
Thu 12 NovVsetín 11:54No data—
Wed 11 NovVsetín 11:54No data—
Tue 10 NovVsetín 11:54No data—
Mon 9 NovVsetín 11:54No data—
Sun 8 NovVsetín 11:54No data—
Sat 7 NovVsetín 11:54No data—
Fri 6 NovVsetín 11:54No data—
Thu 5 NovVsetín 11:54No data—
Wed 4 NovVsetín 11:54No data—
Tue 3 NovVsetín 11:54No data—
Mon 2 NovVsetín 11:54No data—
Sun 1 NovVsetín 11:56No data—
Sat 31 OctVsetín 11:56No data—
Fri 30 OctVsetín 11:56No data—
Thu 29 OctVsetín 11:56No data—
Wed 28 OctVsetín 11:56No data—
Tue 27 OctVsetín 11:56No data—
Mon 26 OctVsetín 11:56No data—
Sun 25 OctVsetín 11:56No data—
Sat 24 OctVsetín 11:56No data—
Fri 23 OctVsetín 11:56No data—
Thu 22 OctVsetín 11:56No data—
Wed 21 OctVsetín 11:56No data—
Tue 20 OctVsetín 11:56No data—
Mon 19 OctVsetín 11:56No data—
Sun 18 OctVsetín 11:56No data—
Sat 17 OctVsetín 11:56No data—
Fri 16 OctVsetín 11:56No data—