Os 9700 9700 Kralupy n.V. – Louny

View line Os 9700

Kralupy n.V. 05:50 → Louny 07:19 Mon, Tue, Wed, Thu, Fri 1 h 29 min · 20 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 05:50 from Kralupy n.V. · Thu 5 Nov

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

Last 30 days

Arrival delay at Louny, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 61 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
05:50on time +1 min
05:53 / 05:54≈ on time ≈ +1 min
05:56≈ on time ≈ +1 min
05:58 / 05:59≈ on time ≈ +1 min
06:02≈ on time ≈ +1 min
06:04≈ on time ≈ +1 min
06:08≈ on time ≈ +1 min
06:12≈ on time ≈ +1 min
06:17≈ on time ≈ +1 min
06:22 / 06:26≈ on time ≈ +1 min
06:32≈ on time ≈ +1 min
06:38 / 06:39≈ on time ≈ +1 min
06:43≈ on time ≈ +1 min
06:47≈ on time ≈ +1 min
06:50≈ on time ≈ +1 min
06:53≈ on time ≈ +1 min
06:57 / 06:59≈ on time ≈ +1 min
07:04≈ on time ≈ +1 min
07:14≈ on time ≈ +1 min
07:19on time +1 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
Wed 4 NovLouny 07:190 min+1 min
Tue 3 NovLouny 07:19+1 min+3 min
Mon 2 NovLouny 07:190 min+1 min
Fri 30 OctLouny 07:20+1 min+4 min
Thu 29 OctLouny 07:20+1 min+3 min
Tue 27 OctLouny 07:200 min+1 min
Mon 26 OctLouny 07:20+1 min+1 min
Fri 23 OctLouny 07:200 min+4 min
Thu 22 OctLouny 07:20+2 min+2 min
Wed 21 OctLouny 07:200 min+1 min
Tue 20 OctLouny 07:200 min—
Mon 19 OctLouny 07:20+2 min+2 min
Fri 16 OctLouny 07:200 min+2 min
Thu 15 OctLouny 07:200 min+1 min
Wed 14 OctLouny 07:20+1 min+1 min
Tue 13 OctLouny 07:200 min+1 min
Mon 12 OctLouny 07:20+1 min+1 min
Fri 9 OctLouny 07:20−1 min+1 min
Thu 8 OctLouny 07:21−1 min+1 min
Wed 7 OctLouny 07:20+1 min+1 min
Tue 6 OctLouny 07:20−1 min+3 min
Mon 5 Oct— 07:35+1 min+2 min
Fri 2 Oct— 07:33−1 min—
Thu 1 Oct— 07:340 min+2 min
Wed 30 Sept— 07:330 min+2 min
Tue 29 Sept— 07:340 min+2 min
Fri 25 Sept— 07:33−1 min+1 min
Thu 24 Sept— 07:32−1 min—
Wed 23 Sept— 07:330 min+2 min
Tue 22 Sept— 07:330 min+2 min