S4 21480 Luzern – Stans

View line S4

Luzern 21:57 → Stans 22:18 Daily 0 h 21 min · 8 stops SBB CFF FFS

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 21:57 from Luzern · Thu 5 Nov

Next departure 21: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%
37/37 runs under 3 min
RT coverage: 37 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

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

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

On-time by weekday

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