S4 21460 Luzern – Stans

View line S4

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

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 15:57 from Luzern · Fri 13 Nov

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 42
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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