Os 9722 9722 Kralupy n.V. – Slaný

View line Os 9722

Kralupy n.V. 06:21 → Slaný 06:55 Mon, Tue, Wed, Thu, Fri 0 h 34 min · 10 stops České dráhy, a.s.

✓ Today’s run finished

Today it reached Slaný at 06:55 −1 min

  1. Kralupy n.V.06:21
  2. Zeměchy06:27
  3. Olovnice06:29
  4. Kamenný Most u Kralup nad Vltavou06:36
  5. Zvoleněves06:39
  6. Slaný předměstí06:50
  7. Slaný06:55

Next service: tomorrow 06:21 from Kralupy n.V. · Fri 6 Nov

Next departure 06:21 tomorrow · Kralupy n.V.
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
98%
61/62 runs under 3 min
RT coverage: 62 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Slaný, in minutes. One bar per run.

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

Worst days

  • Mon 24 Aug Max en route +5 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 21% · 13
  • On time 77% · 48
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=12
  • 100% T n=13
  • 100% W n=12
  • 100% T n=13
  • 100% F n=12
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 62 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
06:21on time +1 min
06:24 / 06:25≈ on time ≈ +1 min
06:27≈ on time ≈ +1 min
06:29 / 06:30≈ on time ≈ +1 min
06:34≈ on time ≈ +1 min
06:36≈ on time ≈ +1 min
06:39 / 06:40≈ on time ≈ on time
06:44 / 06:45≈ on time ≈ on time
06:50≈ 1 min early ≈ on time
06:551 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
Thu 5 NovSlaný 06:59−1 min+1 min
Wed 4 NovSlaný 06:58−2 min—
Tue 3 NovSlaný 06:590 min+1 min
Mon 2 NovSlaný 06:58−2 min+1 min
Fri 30 OctSlaný 06:59−1 min+1 min
Thu 29 OctSlaný 07:000 min+1 min
Tue 27 OctSlaný 07:000 min—
Mon 26 OctSlaný 06:59−1 min+2 min
Fri 23 OctSlaný 06:590 min—
Thu 22 OctSlaný 06:59−1 min+1 min
Wed 21 OctSlaný 06:59+1 min+1 min
Tue 20 OctSlaný 06:56−1 min—
Mon 19 OctSlaný 06:58−1 min+1 min
Fri 16 OctSlaný 06:59−1 min+1 min
Thu 15 OctSlaný 06:58−2 min+1 min
Wed 14 OctSlaný 07:00+1 min+1 min
Tue 13 OctSlaný 06:590 min—
Mon 12 OctSlaný 06:58−2 min—
Fri 9 OctSlaný 06:58−2 min+1 min
Thu 8 OctSlaný 06:58−2 min—
Wed 7 OctSlaný 06:59+1 min+1 min
Tue 6 OctSlaný 06:58−2 min+1 min
Mon 5 Oct— 07:100 min+1 min
Fri 2 Oct— 07:09−1 min+1 min
Thu 1 Oct— 07:09−1 min+2 min
Wed 30 Sept— 07:090 min—
Tue 29 Sept— 07:09−1 min—
Fri 25 Sept— 07:090 min—
Thu 24 Sept— 07:07−2 min+1 min
Wed 23 Sept— 07:090 min+1 min