S4 21456 Luzern → Stans

View line S4

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

S4 21456 Luzern–Stans: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. Expected at Stans: 15:18. TrainsRadar data as of 22 Nov 2026, 15:16 (GMT+1).

Running now · updated 15:16

Position estimated from the timetable

Between Stansstad and Stans 0 min

Estimated arrival at Stans 15:18 · 47 km/h

  1. Luzern14:57
  2. Luzern Allmend/Messe14:59
  3. Kriens Mattenhof15:01
  4. Hergiswil Matt15:06
  5. Hergiswil NW15:09
  6. Stansstad15:13
  7. Stans15:18

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 30 runs arrived on time.

On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
50/50 runs under 3 min
RT coverage: 50 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

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

  • Early 0% · 0
  • On time 100% · 50
  • 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=7
  • 100% T n=7
  • 100% F n=7
  • 100% S n=7
  • 100% S n=8

Stops and timetable

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

Last 90 days, 50 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 10Today
14:57on time on timePassed
14:59≈ on time ≈ on timePassed
15:01≈ on time ≈ on timePassed
15:03≈ on time ≈ on timePassed
15:06≈ on time ≈ on timePassed
15:09 / 15:10≈ on time ≈ on timePassed
15:13 / 15:14≈ on time ≈ +1 minPassed
15:18on time +1 minNext

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
Sun 22 NovStans 15:140 min—
Sat 21 NovStans 15:190 min—
Fri 20 NovStans 15:190 min—
Thu 19 NovStans 15:19+1 min—
Wed 18 NovStans 15:180 min—
Tue 17 NovStans 15:190 min—
Mon 16 NovStans 15:190 min—
Sun 15 NovStans 15:190 min—
Sat 14 NovStans 15:190 min—
Fri 13 NovStans 15:190 min—
Thu 12 NovStans 15:190 min—
Wed 11 NovStans 15:190 min—
Tue 10 NovStans 15:19+1 min—
Mon 9 NovStans 15:190 min—
Sun 8 NovStans 15:190 min—
Sat 7 NovStans 15:190 min—
Fri 6 NovStans 15:190 min—
Thu 5 NovStans 15:190 min—
Wed 4 NovStans 15:190 min—
Tue 3 NovStans 15:190 min—
Mon 2 NovStans 15:190 min—
Sun 1 NovStans 15:190 min—
Sat 31 OctStans 15:190 min—
Fri 30 OctStans 15:20+1 min—
Thu 29 OctStans 15:200 min—
Wed 28 OctStans 15:200 min—
Tue 27 OctStans 15:190 min—
Mon 26 OctStans 15:190 min—
Sun 25 OctStans 15:19+1 min—
Sat 24 OctStans 15:190 min—