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

View line Os 3225

Olomouc hl. n. 15:55 → Vsetín 17:49 Daily 1 h 54 min · 22 stops České dráhy, a.s.

✓ Today’s run finished

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

  1. Olomouc hl. n.15:55
  2. Přerov16:13
  3. Lipník nad Bečvou16:38
  4. Teplice nad Bečvou17:10
  5. Milotice nad Bečvou17:18
  6. Brňov17:35
  7. Vsetín17:49

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

Next departure 15:55 tomorrow · Olomouc hl. n.
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
93%
55/59 runs under 3 min
RT coverage: 59 full · 0 partial · 31 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
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

  • Sun 16 Aug Max en route +10 min · last fix heading to — +4 min
  • Thu 13 Aug Max en route +8 min · last fix heading to — +4 min
  • Fri 2 Oct Max en route +10 min · last fix heading to — +3 min
  • Thu 20 Aug Max en route +7 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 46% · 27
  • On time 47% · 28
  • 3–10 min 7% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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