Os 3904 3904 Valašské Meziříčí – Kojetín

View line Os 3904

Valašské Meziříčí 04:14 → Kojetín 05:54 Daily 1 h 40 min · 18 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Kojetín at 05:54 No data

  1. Valašské Meziříčí04:14
  2. Kunovice-Loučka04:28
  3. Loukov04:41
  4. Jankovice05:07
  5. Holešov05:13
  6. Kroměříž05:41
  7. Kojetín05:54

Next service: tomorrow 04:14 from Valašské Meziříčí · Sun 8 Nov

Next departure 04:14 tomorrow · Valašské Meziříčí
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
100%
57/57 runs under 3 min
RT coverage: 57 full · 0 partial · 33 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 Kojetín, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 5% · 3
  • On time 95% · 54
  • 3–10 min 0% · 0
  • 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
  • 100% T n=8
  • 100% F n=8
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 57 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:14on time +1 min
04:20 / 04:21≈ on time ≈ +1 min
04:24≈ on time ≈ +1 min
04:28 / 04:29≈ on time ≈ +1 min
04:31 / 04:32≈ on time ≈ +1 min
04:37 / 04:38≈ on time ≈ +1 min
04:41≈ on time ≈ +1 min
04:46 / 05:01≈ on time ≈ +1 min
05:05≈ 1 min early ≈ +1 min
05:07≈ 1 min early ≈ +1 min
05:09≈ 1 min early ≈ +1 min
05:13 / 05:15≈ 1 min early ≈ +1 min
05:19≈ 1 min early ≈ +1 min
05:24 / 05:33≈ 1 min early ≈ +1 min
05:41 / 05:42≈ 1 min early ≈ on time
05:46≈ 1 min early ≈ on time
05:49≈ 1 min early ≈ on time
05:541 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
Sat 7 NovKojetín 05:54No data—
Fri 6 NovKojetín 05:54No data—
Thu 5 NovKojetín 05:54No data—
Wed 4 NovKojetín 05:54No data—
Tue 3 NovKojetín 05:55No data—
Mon 2 NovKojetín 05:54No data—
Sun 1 NovKojetín 05:55No data—
Sat 31 OctKojetín 05:55No data—
Fri 30 OctKojetín 05:55No data—
Thu 29 OctKojetín 05:55No data—
Wed 28 OctKojetín 05:56No data—
Tue 27 OctKojetín 05:55No data—
Mon 26 OctKojetín 05:55No data—
Sun 25 OctKojetín 05:55No data—
Sat 24 OctKojetín 05:55No data—
Fri 23 OctKojetín 05:55No data—
Thu 22 OctKojetín 05:55No data—
Wed 21 OctKojetín 05:55No data—
Tue 20 OctKojetín 05:55No data—
Mon 19 OctKojetín 05:55No data—
Sun 18 OctKojetín 05:55No data—
Sat 17 OctKojetín 05:55No data—
Fri 16 OctKojetín 05:55No data—
Thu 15 OctKojetín 05:55No data—
Wed 14 OctKojetín 05:55No data—
Tue 13 OctKojetín 05:55No data—
Mon 12 OctKojetín 05:55No data—
Sun 11 OctKojetín 05:55No data—
Sat 10 OctKojetín 05:55No data—
Fri 9 OctKojetín 05:55No data—