Os 4172 4172 Veselí nad Moravou – Kyjov

View line Os 4172

Veselí nad Moravou 12:25 → Kyjov 12:51 Mon, Tue, Wed, Thu, Fri 0 h 26 min · 6 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 13 November No data

Next service: tomorrow 12:25 from Veselí nad Moravou · Mon 16 Nov

Next departure 12:25 tomorrow · Veselí nad Moravou
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
88%
30/34 runs under 3 min
RT coverage: 34 full · 0 partial · 28 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 Kyjov, in minutes. One bar per run.

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

Worst days

  • Thu 27 Aug Max en route +12 min · last fix heading to — +11 min
  • Fri 28 Aug Max en route +5 min · last fix heading to — +5 min
  • Fri 25 Sept Max en route +4 min · last fix heading to — +4 min
  • Wed 26 Aug Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 30
  • 3–10 min 9% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 86% W n=7
  • 86% T n=7
  • 71% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 34 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
12:25on time +2 min
12:33 / 12:34≈ on time ≈ +2 min
12:38 / 12:39≈ on time ≈ +2 min
12:43≈ on time ≈ +2 min
12:47 / 12:48≈ on time ≈ +2 min
12:51on 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 13 NovKyjov 12:52No data—
Thu 12 NovKyjov 12:52No data—
Wed 11 NovKyjov 12:52No data—
Tue 10 NovKyjov 12:52No data—
Mon 9 NovKyjov 12:52No data—
Fri 6 NovKyjov 12:52No data—
Thu 5 NovKyjov 12:53No data—
Wed 4 NovKyjov 12:52No data—
Tue 3 NovKyjov 12:52No data—
Mon 2 NovKyjov 12:52No data—
Fri 30 OctKyjov 12:52No data—
Thu 29 OctKyjov 12:52No data—
Tue 27 OctKyjov 12:52No data—
Mon 26 OctKyjov 12:52No data—
Fri 23 OctKyjov 12:52No data—
Thu 22 OctKyjov 12:52No data—
Wed 21 OctKyjov 12:52No data—
Tue 20 OctKyjov 12:52No data—
Mon 19 OctKyjov 12:52No data—
Fri 16 OctKyjov 12:52No data—
Thu 15 OctKyjov 12:52No data—
Wed 14 OctKyjov 12:52No data—
Tue 13 OctKyjov 12:52No data—
Mon 12 OctKyjov 12:52No data—
Fri 9 OctKyjov 12:52No data—
Thu 8 OctKyjov 12:52No data—
Wed 7 OctKyjov 12:52No data—
Tue 6 OctKyjov 12:52No data—
Mon 5 Oct— 13:050 min—
Fri 2 Oct— 13:060 min+2 min