Os 3984 3984 Kroměříž → Kojetín

View line Os 3984

Kroměříž 20:42 → Kojetín 20:54 Thu, Fri, Sun 0 h 12 min · 4 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 20 November No data

Next service: tomorrow 20:42 from Kroměříž · Sun 22 Nov

Next departure 20:42 tomorrow · Kroměříž
On-time · 30 days
—
Too little data (0/13 runs with data)
RT coverage: 0 full · 0 partial · 13 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 18 full · 0 partial · 20 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
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

  • Sun 4 Oct Max en route +4 min · last fix heading to — +4 min
  • Thu 1 Oct Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 16
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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
20:42on time +3 min
20:46≈ on time ≈ +3 min
20:49≈ on time ≈ +3 min
20:54on time +2 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 20:54No data—
Thu 19 NovKojetín 20:54No data—
Sun 15 NovKojetín 20:54No data—
Fri 13 NovKojetín 20:54No data—
Thu 12 NovKojetín 20:54No data—
Sun 8 NovKojetín 20:54No data—
Fri 6 NovKojetín 20:54No data—
Thu 5 NovKojetín 20:54No data—
Sun 1 NovKojetín 20:54No data—
Fri 30 OctKojetín 20:55No data—
Thu 29 OctKojetín 20:55No data—
Sun 25 OctKojetín 20:56No data—
Fri 23 OctKojetín 20:55No data—
Thu 22 OctKojetín 20:55No data—
Sun 18 OctKojetín 20:55No data—
Fri 16 OctKojetín 20:55No data—
Thu 15 OctKojetín 20:55No data—
Sun 11 OctKojetín 20:55No data—
Fri 9 OctKojetín 20:55No data—
Thu 8 OctKojetín 20:55No data—
Sun 4 Oct— 21:13+4 min+4 min
Fri 2 Oct— 21:07−1 min—
Thu 1 Oct— 21:11+3 min+4 min
Mon 28 Sept— 21:10+1 min+1 min
Fri 25 Sept— 21:08−1 min—
Thu 24 Sept— 21:07−1 min—
Sun 20 Sept— 21:080 min—
Fri 18 Sept— 21:080 min—
Thu 17 Sept— 21:07−1 min+2 min
Sun 13 Sept— 21:07−1 min—