Os 3211 3211 Olomouc hl. n. – Vsetín

View line Os 3211

Olomouc hl. n. 06:55 → Vsetín 08:49 Mon, Tue, Wed, Thu, Fri 1 h 54 min · 22 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Vsetín at 08:49 No data

  1. Olomouc hl. n.06:55
  2. Přerov07:13
  3. Lipník nad Bečvou07:35
  4. Teplice nad Bečvou08:10
  5. Milotice nad Bečvou08:18
  6. Brňov08:35
  7. Vsetín08:49

Next service: tomorrow 06:55 from Olomouc hl. n. · Fri 6 Nov

Next departure 06:55 tomorrow · Olomouc hl. n.
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
68%
27/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 no data
Typical delay
+1min
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

  • Tue 1 Sept Max en route +7 min · last fix heading to — +7 min
  • Tue 18 Aug Max en route +8 min · last fix heading to — +7 min
  • Thu 24 Sept Max en route +7 min · last fix heading to — +5 min
  • Wed 23 Sept Max en route +8 min · last fix heading to — +5 min
  • Tue 22 Sept Max en route +7 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 8% · 3
  • On time 60% · 24
  • 3–10 min 33% · 13
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 50% T n=8
  • 75% W n=8
  • 63% T n=8
  • 75% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 40 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
06:55on time +2 min
07:00≈ on time ≈ +2 min
07:04 / 07:05≈ on time ≈ +2 min
07:08≈ on time ≈ +2 min
07:13 / 07:24≈ on time ≈ +2 min
07:29≈ +1 min ≈ +2 min
07:32≈ +1 min ≈ +2 min
07:35 / 07:36≈ +1 min ≈ +2 min
07:44≈ +1 min ≈ +2 min
07:49 / 08:02≈ +1 min ≈ +2 min
08:07≈ +1 min ≈ +3 min
08:10≈ +1 min ≈ +3 min
08:13≈ +1 min ≈ +4 min
08:16≈ +1 min ≈ +4 min
08:18 / 08:19≈ +1 min ≈ +4 min
08:21≈ +1 min ≈ +4 min
08:25 / 08:26≈ +1 min ≈ +4 min
08:29 / 08:31≈ +1 min ≈ +4 min
08:35≈ +1 min ≈ +4 min
08:38≈ +1 min ≈ +5 min
08:43≈ +1 min ≈ +5 min
08:49+1 min +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
Thu 5 NovVsetín 08:49No data—
Wed 4 NovVsetín 08:49No data—
Tue 3 NovVsetín 08:49No data—
Mon 2 NovVsetín 08:49No data—
Fri 30 OctVsetín 08:50No data—
Thu 29 OctVsetín 08:50No data—
Tue 27 OctVsetín 08:50No data—
Mon 26 OctVsetín 08:50No data—
Fri 23 OctVsetín 08:51No data—
Thu 22 OctVsetín 08:51No data—
Wed 21 OctVsetín 08:50No data—
Tue 20 OctVsetín 08:50No data—
Mon 19 OctVsetín 08:50No data—
Fri 16 OctVsetín 08:51No data—
Thu 15 OctVsetín 08:51No data—
Wed 14 OctVsetín 08:50No data—
Tue 13 OctVsetín 08:50No data—
Mon 12 OctVsetín 08:50No data—
Fri 9 OctVsetín 08:50No data—
Thu 8 OctVsetín 08:50No data—
Wed 7 OctVsetín 08:50No data—
Tue 6 OctVsetín 08:50No data—
Mon 5 Oct— 08:20+2 min+2 min
Fri 2 Oct— 08:41+2 min+3 min
Thu 1 Oct— 08:170 min—
Wed 30 Sept— 08:170 min+2 min
Tue 29 Sept— 08:21+4 min+5 min
Fri 25 Sept— 08:190 min+4 min
Thu 24 Sept— 08:23+5 min+7 min
Wed 23 Sept— 08:22+5 min+8 min