S9 21991 Hochdorf – Luzern

View line S9

Hochdorf 00:01 → Luzern 00:28 Daily 0 h 27 min · 8 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Luzern at 00:30 +2 min

  1. Hochdorf00:01
  2. Hochdorf Schönau00:02
  3. Ballwil00:05
  4. Waldibrücke00:13
  5. Emmenbrücke Gersag00:18
  6. Emmenbrücke00:20
  7. Luzern00:28

Next service: tomorrow 00:01 from Hochdorf · Tue 17 Nov

Next departure 00:01 tomorrow · Hochdorf
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
64/64 runs under 3 min
RT coverage: 64 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

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

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

  • Early 11% · 7
  • On time 89% · 57
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 100% W n=11
  • 100% T n=9
  • 100% F n=11
  • 100% S n=9
  • 100% S n=8

Stops and timetable

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

Last 90 days, 64 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
00:01on time +1 min
00:02≈ on time ≈ +1 min
00:05≈ on time ≈ +1 min
00:08≈ on time ≈ +1 min
00:13≈ on time ≈ +1 min
00:18≈ on time ≈ +1 min
00:20≈ on time ≈ +2 min
00:28on 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
Mon 16 NovLuzern 00:29+2 min+2 min
Sun 15 NovLuzern 00:29−1 min—
Sat 14 NovLuzern 00:29+1 min—
Fri 13 NovLuzern 00:29−1 min—
Thu 12 NovLuzern 00:28−1 min—
Wed 11 NovLuzern 00:290 min—
Tue 10 NovLuzern 00:28−2 min—
Mon 9 NovLuzern 00:28−2 min—
Sun 8 NovLuzern 00:29−1 min—
Sat 7 NovLuzern 00:29+1 min—
Fri 6 NovLuzern 00:290 min—
Thu 5 NovLuzern 00:290 min—
Wed 4 NovLuzern 00:27−2 min—
Tue 3 NovLuzern 00:29+1 min—
Mon 2 NovLuzern 00:29−1 min—
Sun 1 NovLuzern 00:30+1 min+1 min
Sat 31 OctLuzern 00:31+2 min+2 min
Fri 30 OctLuzern 00:27−2 min—
Thu 29 OctLuzern 00:27−2 min—
Wed 28 OctLuzern 00:28−1 min—
Tue 27 OctLuzern 00:290 min—
Mon 26 OctLuzern 00:290 min+1 min
Sun 25 OctLuzern 00:31+2 min+2 min
Sat 24 OctLuzern 00:32+3 min+3 min
Fri 23 OctLuzern 00:290 min—
Thu 22 OctLuzern 00:30+1 min+1 min
Wed 21 OctLuzern 00:290 min—
Tue 20 OctLuzern 00:30+1 min+1 min
Mon 19 OctLuzern 00:290 min—
Sun 18 OctLuzern 00:28−1 min—