S4 21417 Wolfenschiessen – Luzern

View line S4

Wolfenschiessen 04:53 → Luzern 05:22 Daily 0 h 29 min · 10 stops zb Zentralbahn

✓ Today’s run finished

Today it reached Luzern at 05:22 0 min

  1. Wolfenschiessen04:53
  2. Stans05:01
  3. Stansstad05:04
  4. Hergiswil Matt05:11
  5. Horw05:14
  6. Luzern Allmend/Messe05:18
  7. Luzern05:22

Next service: tomorrow 04:53 from Wolfenschiessen · Thu 19 Nov

Next departure 04:53 tomorrow · Wolfenschiessen
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%
46/47 runs under 3 min
RT coverage: 47 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: +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

Worst days

  • Tue 17 Nov Max en route +25 min · last fix heading to Luzern +25 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 94% · 44
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 47 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
04:53on time on time
04:56≈ on time ≈ on time
05:01≈ on time ≈ on time
05:04 / 05:05≈ on time ≈ on time
05:08 / 05:09≈ on time ≈ on time
05:11≈ on time ≈ on time
05:14≈ on time ≈ +1 min
05:16≈ on time ≈ +1 min
05:18≈ on time ≈ +1 min
05: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
Wed 18 NovLuzern 05:230 min—
Tue 17 NovLuzern 05:47+25 min+25 min
Mon 16 NovLuzern 05:230 min—
Sun 15 NovLuzern 05:240 min—
Sat 14 NovLuzern 05:22−1 min—
Fri 13 NovLuzern 05:25+1 min+1 min
Thu 12 NovLuzern 05:230 min—
Wed 11 NovLuzern 05:230 min—
Tue 10 NovLuzern 05:230 min—
Mon 9 NovLuzern 05:22−1 min—
Sun 8 NovLuzern 05:220 min—
Sat 7 NovLuzern 05:230 min—
Fri 6 NovLuzern 05:23−1 min—
Thu 5 NovLuzern 05:230 min—
Wed 4 NovLuzern 05:22−1 min—
Tue 3 NovLuzern 05:22−1 min—
Mon 2 NovLuzern 05:24+1 min+1 min
Sun 1 NovLuzern 05:22−1 min—
Sat 31 OctLuzern 05:24+1 min—
Fri 30 OctLuzern 05:230 min—
Thu 29 OctLuzern 05:22−1 min—
Wed 28 OctLuzern 05:24+1 min—
Tue 27 OctLuzern 05:23−1 min—
Mon 26 OctLuzern 05:220 min—
Sun 25 OctLuzern 05:230 min—
Sat 24 OctLuzern 05:22−1 min—
Fri 23 OctLuzern 05:22−1 min—
Thu 22 OctLuzern 05:24+1 min—
Wed 21 OctLuzern 05:230 min—
Tue 20 OctLuzern 05:220 min—