S4 21440 Luzern – Stans

View line S4

Luzern 10:57 → Stans 11:18 Daily 0 h 21 min · 8 stops zb Zentralbahn

It has not run yet today

Last recorded run: Tuesday 17 November No data

Next service: today 10:57 from Luzern · Wed 18 Nov

Next departure 10:57 today · Luzern
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 5 no data
On-time · 90 days
97%
38/39 runs under 3 min
RT coverage: 39 full · 0 partial · 6 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 Stans, 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 5 Oct Max en route +4 min · last fix heading to Stansstad +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 75% M n=4
  • 100% T n=6
  • 100% W n=6
  • 100% T n=4
  • 100% F n=6
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 39 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
10:57on time on time
10:59≈ on time ≈ on time
11:01≈ on time ≈ on time
11:03≈ on time ≈ on time
11:06≈ on time ≈ on time
11:09 / 11:10≈ on time ≈ on time
11:13 / 11:14≈ on time ≈ +1 min
11:18on 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
Tue 17 NovStans 11:19No data—
Mon 16 NovStans 11:180 min—
Sun 15 NovStans 11:19+1 min+1 min
Sat 14 NovStans 11:190 min—
Fri 13 NovStans 11:190 min—
Thu 12 NovStans 11:19No data—
Wed 11 NovStans 11:190 min—
Tue 10 NovStans 11:190 min—
Mon 9 NovStans 11:19No data—
Sun 8 NovStans 11:19+1 min—
Sat 7 NovStans 11:190 min—
Fri 6 NovStans 11:190 min—
Thu 5 NovStans 11:190 min—
Wed 4 NovStans 11:190 min—
Tue 3 NovStans 11:190 min—
Mon 2 NovStans 11:19No data—
Sun 1 NovStans 11:190 min—
Sat 31 OctStans 11:180 min—
Fri 30 OctStans 11:20+1 min—
Thu 29 OctStans 11:19No data—
Wed 28 OctStans 11:190 min—
Tue 27 OctStans 11:190 min—
Mon 26 OctStans 11:200 min—
Sun 25 OctStans 11:190 min—
Sat 24 OctStans 11:20+1 min+1 min
Fri 23 OctStans 11:190 min—
Thu 22 OctStans 11:190 min—
Wed 21 OctStans 11:190 min—
Tue 20 OctStans 11:190 min—
Mon 19 OctStans 11:190 min—