S4 21463 Stans – Luzern

View line S4

Stans 16:40 → Luzern 17:01 Daily 0 h 21 min · 8 stops zb Zentralbahn

✓ Today’s run finished

Today it reached Luzern at 17:01 0 min

  1. Stans16:40
  2. Stansstad16:43
  3. Hergiswil NW16:47
  4. Horw16:53
  5. Kriens Mattenhof16:55
  6. Luzern Allmend/Messe16:57
  7. Luzern17:01

Next service: tomorrow 16:40 from Stans · Sat 7 Nov

Next departure 16:40 tomorrow · Stans
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%
38/38 runs under 3 min
RT coverage: 38 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 Luzern, 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

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

  • Early 0% · 0
  • On time 100% · 38
  • 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=5
  • 100% W n=5
  • 100% T n=6
  • 100% F n=6
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 38 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
16:40on time on time
16:43 / 16:44≈ on time ≈ on time
16:47 / 16:48≈ on time ≈ on time
16:50≈ on time ≈ on time
16:53≈ on time ≈ +1 min
16:55≈ on time ≈ +1 min
16:57≈ on time ≈ +1 min
17:01on 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 NovLuzern 17:020 min—
Thu 5 NovLuzern 17:03+1 min—
Wed 4 NovLuzern 17:020 min—
Tue 3 NovLuzern 17:020 min—
Mon 2 NovLuzern 17:020 min—
Sun 1 NovLuzern 17:020 min—
Sat 31 OctLuzern 17:020 min—
Fri 30 OctLuzern 17:020 min—
Thu 29 OctLuzern 17:03+1 min+1 min
Wed 28 OctLuzern 17:03+1 min—
Tue 27 OctLuzern 17:03+1 min+1 min
Mon 26 OctLuzern 17:020 min—
Sun 25 OctLuzern 17:020 min—
Sat 24 OctLuzern 17:01−1 min—
Fri 23 OctLuzern 17:010 min—
Thu 22 OctLuzern 17:020 min—
Wed 21 OctLuzern 17:020 min—
Tue 20 OctLuzern 17:020 min—
Mon 19 OctLuzern 17:020 min—
Sun 18 OctLuzern 17:020 min—
Sat 17 OctLuzern 17:020 min—
Fri 16 OctLuzern 17:020 min—
Thu 15 OctLuzern 17:04+2 min+2 min
Wed 14 OctLuzern 17:03+1 min—
Tue 13 OctLuzern 17:03+1 min—
Mon 12 OctLuzern 17:020 min—
Sun 11 OctLuzern 17:01−1 min—
Sat 10 OctLuzern 17:020 min—
Fri 9 OctLuzern 17:030 min—
Thu 8 OctLuzern 17:020 min—