Os 3980 3980 Kroměříž – Kojetín

View line Os 3980

Kroměříž 04:10 → Kojetín 04:22 Mon, Tue, Wed, Thu, Fri 0 h 12 min · 4 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Kojetín at 04:23 No data

  1. Kroměříž04:10
  2. Postoupky04:14
  3. Bezměrov04:17
  4. Kojetín04:22

Next service: Monday 04:10 from Kroměříž · Mon 23 Nov

Next departure 04:10 Monday · Kroměříž
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 32 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 Kojetí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

  • Mon 7 Sept Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 93% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 30 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:10on time on time
04:14≈ on time ≈ on time
04:17≈ on time ≈ +1 min
04:22on 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
Fri 20 NovKojetín 04:23No data—
Thu 19 NovKojetín 04:23No data—
Wed 18 NovKojetín 04:23No data—
Mon 16 NovKojetín 04:24No data—
Fri 13 NovKojetín 04:23No data—
Thu 12 NovKojetín 04:23No data—
Wed 11 NovKojetín 04:23No data—
Tue 10 NovKojetín 04:23No data—
Mon 9 NovKojetín 04:23No data—
Fri 6 NovKojetín 04:23No data—
Thu 5 NovKojetín 04:23No data—
Wed 4 NovKojetín 04:23No data—
Tue 3 NovKojetín 04:23No data—
Mon 2 NovKojetín 04:23No data—
Fri 30 OctKojetín 04:23No data—
Thu 29 OctKojetín 04:23No data—
Tue 27 OctKojetín 04:23No data—
Mon 26 OctKojetín 04:23No data—
Fri 23 OctKojetín 04:23No data—
Thu 22 OctKojetín 04:23No data—
Wed 21 OctKojetín 04:23No data—
Tue 20 OctKojetín 04:23No data—
Mon 19 OctKojetín 04:23No data—
Fri 16 OctKojetín 04:23No data—
Thu 15 OctKojetín 04:23No data—
Wed 14 OctKojetín 04:23No data—
Tue 13 OctKojetín 04:23No data—
Mon 12 OctKojetín 04:23No data—
Fri 9 OctKojetín 04:23No data—
Thu 8 OctKojetín 04:23No data—