S4 21496 Luzern – Stans

View line S4

Luzern 01:02 → Stans 01:22 Daily 0 h 20 min · 8 stops zb Zentralbahn

✓ Today’s run finished

Today it reached Stans at 01:22 0 min

  1. Luzern01:02
  2. Luzern Allmend/Messe01:04
  3. Kriens Mattenhof01:06
  4. Hergiswil Matt01:11
  5. Hergiswil NW01:14
  6. Stansstad01:18
  7. Stans01:22

Next service: tomorrow 01:02 from Luzern · Sat 7 Nov

Next departure 01:02 tomorrow · Luzern
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
95%
42/44 runs under 3 min
RT coverage: 44 full · 0 partial · 1 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: +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 24 Oct Max en route +9 min · last fix heading to Stans +9 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Stans +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 42
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 80% W n=5
  • 100% T n=5
  • 100% F n=9
  • 75% S n=4
  • 100% S n=7

Stops and timetable

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

Last 90 days, 44 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
01:02on time on time
01:04≈ on time ≈ on time
01:06≈ on time ≈ on time
01:08≈ on time ≈ on time
01:11≈ on time ≈ on time
01:14≈ on time ≈ +1 min
01:18≈ on time ≈ +1 min
01:22on 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 01:230 min—
Thu 5 NovStans 01:230 min—
Wed 4 NovStans 01:28+5 min+5 min
Tue 3 NovStans 01:240 min—
Mon 2 NovStans 01:24+1 min—
Sun 1 NovStans 01:230 min—
Sat 31 OctStans 01:230 min—
Fri 30 OctStans 01:22−1 min—
Thu 29 OctStans 01:230 min—
Wed 28 OctStans 01:230 min—
Tue 27 OctStans 01:230 min—
Mon 26 OctStans 01:230 min—
Sun 25 OctStans 01:24+1 min+1 min
Sat 24 OctStans 01:32+9 min+9 min
Fri 23 OctStans 01:230 min—
Thu 22 OctStans 01:230 min—
Wed 21 OctStans 01:230 min—
Tue 20 OctStans 01:230 min—
Mon 19 OctStansstad 01:190 min—
Sun 18 OctStansstad 01:200 min—
Sat 17 OctStansstad 01:19−1 min—
Fri 16 OctStansstad 01:190 min—
Thu 15 OctStansstad 01:190 min—
Wed 14 OctStansstad 01:190 min—
Tue 13 OctStansstad 01:190 min—
Mon 12 OctStansstad 01:19No data—
Sun 11 OctStansstad 01:21+2 min+2 min
Sat 10 OctStansstad 01:21+2 min+2 min
Fri 9 OctStansstad 01:190 min—
Thu 8 OctStansstad 01:190 min—