S4 21448 Luzern – Stans

View line S4

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 12:57 from Luzern · Sat 7 Nov

Next departure 12:57 today · Luzern
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 31 full · 0 partial · 7 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

  • Sun 6 Sept Max en route +4 min · last fix heading to Wolfenschiessen +4 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 94% · 29
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=5
  • 100% W n=6
  • 100% T n=3
  • 100% F n=5
  • 100% S n=5
  • 83% S n=6

Stops and timetable

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

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