S4 21468 Luzern – Stans

View line S4

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

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 17:57 from Luzern · Sat 14 Nov

Next departure 17:57 today · Luzern
On-time · 30 days
86%
25/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
91%
43/47 runs under 3 min
RT coverage: 47 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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 2 Nov Max en route +3 min · last fix heading to Stans +3 min
  • Tue 27 Oct Max en route +3 min · last fix heading to Stans +3 min
  • Thu 22 Oct Max en route +3 min · last fix heading to Stans +3 min
  • Fri 16 Oct Max en route +3 min · last fix heading to Stansstad +3 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 89% · 42
  • 3–10 min 9% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 88% T n=8
  • 100% W n=8
  • 86% T n=7
  • 83% F n=6
  • 100% S n=5
  • 100% S n=6

Stops and timetable

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

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