Os 14620 14620 Břeclav → Šakvice

View line Os 14620

Břeclav 18:31 → Šakvice 18:56 Daily 0 h 25 min · 6 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Friday 20 November No data

Next service: today 18:31 from Břeclav · Sat 21 Nov

Next departure 18:31 today · Břeclav
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
98%
41/42 runs under 3 min
RT coverage: 42 full · 0 partial · 47 no data
Typical delay
−1min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Šakvice, in minutes. One bar per run.

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

Worst days

  • Tue 1 Sept Max en route +10 min · last fix heading to — +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 41
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 42 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:31on time +2 min
18:36 / 18:37≈ on time ≈ +2 min
18:40 / 18:41≈ on time ≈ +1 min
18:44≈ 1 min early ≈ +1 min
18:48 / 18:51≈ 1 min early ≈ +1 min
18:561 min early 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
Fri 20 NovŠakvice 18:57No data—
Thu 19 NovŠakvice 18:57No data—
Wed 18 NovŠakvice 18:57No data—
Tue 17 NovŠakvice 18:57No data—
Mon 16 NovŠakvice 18:57No data—
Sun 15 NovŠakvice 18:57No data—
Sat 14 NovŠakvice 18:58No data—
Fri 13 NovŠakvice 18:57No data—
Thu 12 NovŠakvice 18:57No data—
Wed 11 NovŠakvice 18:57No data—
Tue 10 NovŠakvice 18:57No data—
Mon 9 NovŠakvice 18:57No data—
Sun 8 NovŠakvice 18:57No data—
Sat 7 NovŠakvice 18:57No data—
Fri 6 NovŠakvice 18:57No data—
Thu 5 NovŠakvice 18:57No data—
Wed 4 NovŠakvice 18:57No data—
Tue 3 NovŠakvice 18:57No data—
Mon 2 NovŠakvice 18:57No data—
Sun 1 NovŠakvice 18:57No data—
Sat 31 OctŠakvice 18:57No data—
Fri 30 OctŠakvice 18:57No data—
Thu 29 OctŠakvice 18:57No data—
Wed 28 OctŠakvice 18:57No data—
Tue 27 OctŠakvice 18:58No data—
Mon 26 OctŠakvice 18:57No data—
Sun 25 OctŠakvice 18:57No data—
Sat 24 OctŠakvice 18:58No data—
Fri 23 OctŠakvice 18:58No data—
Thu 22 OctŠakvice 18:57No data—