Os 4732 4732 Holubice – Skalice n. Svit.

View line Os 4732

Holubice 14:53 → Skalice n. Svit. 16:19 Mon, Tue, Wed, Thu, Fri 1 h 26 min · 19 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 14:53 from Holubice · Fri 6 Nov

Next departure 14:53 today · Holubice
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
95%
38/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 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 Skalice n. Svit., 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 +7 min · last fix heading to — +7 min
  • Tue 1 Sept Max en route +7 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 38
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 88% T n=8
  • 100% W n=8
  • 88% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 40 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
14:537 min early 5 min early
14:57 / 14:58≈ 7 min early ≈ 4 min early
15:00 / 15:01≈ 6 min early ≈ 4 min early
15:03 / 15:04≈ 6 min early ≈ 4 min early
15:07≈ 6 min early ≈ 3 min early
15:09 / 15:10≈ 5 min early ≈ 3 min early
15:15 / 15:16≈ 5 min early ≈ 3 min early
15:27 / 15:30≈ 3 min early ≈ 1 min early
15:34 / 15:35≈ 3 min early ≈ on time
15:40 / 15:41≈ 3 min early ≈ on time
15:45≈ 3 min early ≈ on time
15:48 / 15:49≈ 2 min early ≈ on time
15:50 / 15:51≈ 2 min early ≈ on time
15:56 / 15:57≈ 2 min early ≈ on time
15:59 / 16:00≈ 2 min early ≈ on time
16:02 / 16:03≈ 1 min early ≈ on time
16:06 / 16:10≈ 1 min early ≈ +1 min
16:13≈ on time ≈ +1 min
16:19on 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
Thu 5 NovSkalice n. Svit. 16:19No data—
Wed 4 NovSkalice n. Svit. 16:19No data—
Tue 3 NovSkalice n. Svit. 16:19No data—
Mon 2 NovSkalice n. Svit. 16:19No data—
Fri 30 OctSkalice n. Svit. 16:20No data—
Thu 29 OctSkalice n. Svit. 16:20No data—
Tue 27 OctSkalice n. Svit. 16:20No data—
Mon 26 OctSkalice n. Svit. 16:20No data—
Fri 23 OctSkalice n. Svit. 16:20No data—
Thu 22 OctSkalice n. Svit. 16:20No data—
Wed 21 OctSkalice n. Svit. 16:20No data—
Tue 20 OctSkalice n. Svit. 16:20No data—
Mon 19 OctSkalice n. Svit. 16:20No data—
Fri 16 OctSkalice n. Svit. 16:20No data—
Thu 15 OctSkalice n. Svit. 16:20No data—
Wed 14 OctSkalice n. Svit. 16:20No data—
Tue 13 OctSkalice n. Svit. 16:20No data—
Mon 12 OctSkalice n. Svit. 16:20No data—
Fri 9 OctSkalice n. Svit. 16:20No data—
Thu 8 OctSkalice n. Svit. 16:20No data—
Wed 7 OctSkalice n. Svit. 16:20No data—
Tue 6 OctSkalice n. Svit. 16:20No data—
Mon 5 Oct— 16:35+2 min+3 min
Fri 2 Oct— 16:330 min+3 min
Thu 1 Oct— 16:340 min+7 min
Wed 30 Sept— 16:33−1 min+2 min
Tue 29 Sept— 16:330 min+5 min
Fri 25 Sept— 16:340 min+2 min
Thu 24 Sept— 16:32−1 min+1 min
Wed 23 Sept— 16:36+2 min+2 min