S9 21951 Lenzburg → Luzern

View line S9

Lenzburg 13:04 → Luzern 14:28 Daily 1 h 24 min · 21 stops SBB CFF FFS

S9 21951 Lenzburg–Luzern: final delay under 3 min on 20 of its 21 runs with data in the last 30 days (95%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 06:35 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 13:04 from Lenzburg · Sun 22 Nov

Next departure 13:04 today · Lenzburg
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 8 no data
On-time · 90 days
96%
46/48 runs under 3 min
RT coverage: 48 full · 0 partial · 12 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

Worst days

  • Fri 6 Nov Max en route +18 min · last fix heading to Luzern +18 min
  • Sat 5 Sept Max en route +6 min · last fix heading to Luzern +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 46
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 48 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
13:04on time on time
13:09≈ on time ≈ on time
13:11≈ on time ≈ on time
13:15≈ on time ≈ on time
13:18≈ on time ≈ on time
13:23≈ on time ≈ +1 min
13:27 / 13:28≈ on time ≈ +1 min
13:31≈ on time ≈ +1 min
13:35≈ on time ≈ +1 min
13:39 / 13:43≈ on time ≈ +1 min
13:45≈ on time ≈ +1 min
13:50≈ on time ≈ +1 min
13:52≈ on time ≈ +1 min
13:56 / 13:59≈ on time ≈ +1 min
14:00≈ on time ≈ +1 min
14:03≈ on time ≈ +2 min
14:07≈ on time ≈ +2 min
14:12 / 14:13≈ on time ≈ +2 min
14:18≈ on time ≈ +2 min
14:20≈ on time ≈ +2 min
14: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
Sat 21 NovLuzern 14:280 min—
Fri 20 NovLuzern 14:29+1 min—
Thu 19 NovLuzern 14:29No data—
Wed 18 NovLuzern 14:29+2 min+2 min
Tue 17 NovLuzern 14:29+1 min—
Mon 16 NovLuzern 14:29No data—
Sun 15 NovLuzern 14:290 min—
Sat 14 NovLuzern 14:29+1 min+1 min
Fri 13 NovLuzern 14:29+1 min—
Thu 12 NovLuzern 14:29No data—
Wed 11 NovLuzern 14:290 min—
Tue 10 NovLuzern 14:29+1 min—
Mon 9 NovLuzern 14:29No data—
Sun 8 NovLuzern 14:28−1 min—
Sat 7 NovLuzern 14:290 min—
Fri 6 NovLuzern 14:47+18 min+18 min
Thu 5 NovLuzern 14:29No data—
Wed 4 NovLuzern 14:290 min—
Tue 3 NovLuzern 14:29+1 min+1 min
Mon 2 NovLuzern 14:29No data—
Sun 1 NovLuzern 14:290 min—
Sat 31 OctLuzern 14:290 min—
Fri 30 OctLuzern 14:31+2 min+2 min
Thu 29 OctLuzern 14:29No data—
Wed 28 OctLuzern 14:290 min—
Tue 27 OctLuzern 14:290 min—
Mon 26 OctLuzern 14:29No data—
Sun 25 OctLuzern 14:31+2 min+2 min
Sat 24 OctLuzern 14:290 min—
Fri 23 OctLuzern 14:31+2 min+2 min