S4 21444 Luzern – Stans

View line S4

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

✓ Today’s run finished

Today, last fix heading to Stans at 12:19 No data

  1. Luzern11:57
  2. Luzern Allmend/Messe11:59
  3. Kriens Mattenhof12:01
  4. Hergiswil Matt12:06
  5. Hergiswil NW12:09
  6. Stansstad12:13
  7. Stans12:18

Next service: tomorrow 11:57 from Luzern · Fri 13 Nov

Next departure 11:57 tomorrow · Luzern
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
100%
31/31 runs under 3 min
RT coverage: 31 full · 0 partial · 10 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

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

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

On-time by weekday

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