S4 21435 Stans – Luzern

View line S4

Stans 09:40 → Luzern 10:01 Daily 0 h 21 min · 8 stops zb Zentralbahn

✓ Today’s run finished

Today it reached Luzern at 10:01 0 min

  1. Stans09:40
  2. Stansstad09:43
  3. Hergiswil NW09:47
  4. Horw09:53
  5. Kriens Mattenhof09:55
  6. Luzern Allmend/Messe09:57
  7. Luzern10:01

Next service: tomorrow 09:40 from Stans · Fri 6 Nov

Next departure 09:40 tomorrow · Stans
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 34 full · 0 partial · 1 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 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

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

  • Early 3% · 1
  • On time 97% · 33
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=5
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 34 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
09:40on time on time
09:43 / 09:44≈ on time ≈ on time
09:47 / 09:48≈ on time ≈ on time
09:50≈ on time ≈ on time
09:53≈ on time ≈ +1 min
09:55≈ on time ≈ +1 min
09:57≈ on time ≈ +1 min
10:01on 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
Thu 5 NovLuzern 10:020 min—
Wed 4 NovLuzern 10:02−1 min—
Tue 3 NovLuzern 10:020 min—
Mon 2 NovLuzern 10:020 min—
Sun 1 NovLuzern 10:020 min—
Sat 31 OctLuzern 10:020 min—
Fri 30 OctLuzern 10:020 min—
Thu 29 OctLuzern 10:02No data—
Wed 28 OctLuzern 10:020 min—
Tue 27 OctLuzern 10:04+2 min+2 min
Mon 26 OctStans 11:010 min—
Sun 25 OctLuzern 10:03+1 min+1 min
Sat 24 OctLuzern 10:020 min—
Fri 23 OctLuzern 10:020 min—
Thu 22 OctLuzern 10:020 min—
Wed 21 OctLuzern 10:020 min—
Tue 20 OctLuzern 10:05+3 min+3 min
Mon 19 OctLuzern 10:03+2 min+2 min
Sun 18 OctLuzern 10:020 min—
Sat 17 OctLuzern 10:020 min—
Fri 16 OctLuzern 10:01−1 min—
Thu 15 OctLuzern 10:020 min—
Wed 14 OctLuzern 10:01−1 min—
Tue 13 OctLuzern 10:030 min—
Mon 12 OctLuzern 10:01−1 min—
Sun 11 OctLuzern 10:02−1 min—
Sat 10 OctLuzern 10:030 min—
Fri 9 OctLuzern 10:020 min—
Thu 8 OctLuzern 10:020 min—
Wed 7 OctLuzern 10:020 min—