Os 4180 4180 Veselí nad Moravou – Kyjov

View line Os 4180

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

It has not run yet today

Last recorded run: Sunday 15 November No data

Next service: today 18:25 from Veselí nad Moravou · Mon 16 Nov

Next departure 18:25 today · Veselí nad Moravou
On-time · 30 days
—
Too little data (0/25 runs with data)
RT coverage: 0 full · 0 partial · 25 no data
On-time · 90 days
100%
39/39 runs under 3 min
RT coverage: 39 full · 0 partial · 36 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 39
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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