EN 477 477 Břeclav – Kúty

View line EN 477

Břeclav 04:53 → Kúty 05:05 Daily 0 h 12 min · 4 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Kúty at 05:04 No data

  1. Břeclav04:53
  2. Lanžhot04:58
  3. Brodské z05:02
  4. Kúty05:05

Next service: tomorrow 04:53 from Břeclav · Sat 21 Nov

Next departure 04:53 tomorrow · Břeclav
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
43%
19/44 runs under 3 min
RT coverage: 44 full · 0 partial · 46 no data
Typical delay
+4min
Median at arrival, 90 days
P90
+41min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Kúty, in minutes. One bar per run.

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

Worst days

  • Wed 26 Aug Max en route +94 min · last fix heading to — +94 min
  • Tue 15 Sept Max en route +60 min · last fix heading to — +60 min
  • Sun 23 Aug Max en route +54 min · last fix heading to — +54 min
  • Tue 29 Sept Max en route +44 min · last fix heading to — +44 min
  • Sat 5 Sept Max en route +42 min · last fix heading to — +42 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 43% · 19
  • 3–10 min 16% · 7
  • 10–30 min 23% · 10
  • 30+ min 18% · 8

On-time by weekday

  • 57% M n=7
  • 50% T n=6
  • 50% W n=6
  • 50% T n=6
  • 33% F n=6
  • 0% S n=6
  • 57% S n=7

Stops and timetable

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

Last 90 days, 44 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:53+2 min +39 min
04:58≈ +3 min ≈ +40 min
05:02≈ +4 min ≈ +40 min
05:05+4 min +41 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 NovKúty 05:04No data—
Thu 19 NovKúty 05:04No data—
Wed 18 NovKúty 05:04No data—
Tue 17 NovKúty 05:05No data—
Mon 16 NovKúty 05:05No data—
Sun 15 NovKúty 05:04No data—
Sat 14 NovKúty 05:04No data—
Fri 13 NovKúty 05:04No data—
Thu 12 NovKúty 05:04No data—
Wed 11 NovKúty 05:04No data—
Tue 10 NovKúty 05:04No data—
Mon 9 NovKúty 05:04No data—
Sun 8 NovKúty 05:04No data—
Sat 7 NovKúty 05:04No data—
Fri 6 NovKúty 05:04No data—
Thu 5 NovKúty 05:04No data—
Wed 4 NovKúty 05:04No data—
Tue 3 NovKúty 05:05No data—
Mon 2 NovKúty 05:04No data—
Sun 1 NovKúty 05:06No data—
Sat 31 OctKúty 05:06No data—
Fri 30 OctKúty 05:06No data—
Thu 29 OctKúty 05:06No data—
Wed 28 OctKúty 05:07No data—
Tue 27 OctKúty 05:06No data—
Mon 26 OctKúty 05:06No data—
Sun 25 OctKúty 05:06No data—
Sat 24 OctKúty 05:06No data—
Fri 23 OctKúty 05:06No data—
Thu 22 OctKúty 05:06No data—