S4 21424 Luzern – Stans

View line S4

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

✓ Today’s run finished

Today it reached Stans at 07:18 0 min

  1. Luzern06:57
  2. Luzern Allmend/Messe06:59
  3. Kriens Mattenhof07:01
  4. Hergiswil Matt07:06
  5. Hergiswil NW07:09
  6. Stansstad07:13
  7. Stans07:18

Next service: tomorrow 06:57 from Luzern · Sat 14 Nov

Next departure 06:57 tomorrow · Luzern
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
48/49 runs under 3 min
RT coverage: 49 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Sat 31 Oct Max en route +3 min · last fix heading to Stans +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 48
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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