S4 21425 Wolfenschiessen – Luzern

View line S4

Wolfenschiessen 07:01 → Luzern 07:31 Daily 0 h 30 min · 10 stops zb Zentralbahn

✓ Today’s run finished

Today it reached Luzern at 07:31 0 min

  1. Wolfenschiessen07:01
  2. Stans07:09
  3. Stansstad07:13
  4. Hergiswil Matt07:20
  5. Horw07:23
  6. Luzern Allmend/Messe07:27
  7. Luzern07:31

Next service: tomorrow 07:01 from Wolfenschiessen · Sat 14 Nov

Next departure 07:01 tomorrow · Wolfenschiessen
On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
45/47 runs under 3 min
RT coverage: 47 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Mon 19 Oct Max en route +9 min · last fix heading to Luzern +9 min
  • Wed 11 Nov Max en route +5 min · last fix heading to Luzern +5 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 91% · 43
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
07:01on time on time
07:04≈ on time ≈ on time
07:09 / 07:10≈ on time ≈ +1 min
07:13 / 07:14≈ on time ≈ +1 min
07:17 / 07:18≈ on time ≈ +1 min
07:20≈ on time ≈ +1 min
07:23≈ on time ≈ +1 min
07:25≈ on time ≈ +2 min
07:27≈ on time ≈ +2 min
07:31on time +2 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 13 NovLuzern 07:320 min—
Thu 12 NovLuzern 07:320 min—
Wed 11 NovLuzern 07:37+5 min+5 min
Tue 10 NovLuzern 07:320 min—
Mon 9 NovLuzern 07:290 min—
Sun 8 NovLuzern 07:33+1 min—
Sat 7 NovLuzern 07:29−1 min—
Fri 6 NovLuzern 07:33+1 min—
Thu 5 NovLuzern 07:33+1 min+1 min
Wed 4 NovLuzern 07:320 min—
Tue 3 NovLuzern 07:290 min—
Mon 2 NovLuzern 07:33+1 min—
Sun 1 NovLuzern 07:31−1 min—
Sat 31 OctLuzern 07:320 min—
Fri 30 OctLuzern 07:320 min—
Thu 29 OctLuzern 07:320 min—
Wed 28 OctLuzern 07:35+3 min+3 min
Tue 27 OctLuzern 07:320 min—
Mon 26 OctLuzern 07:35+3 min+3 min
Sun 25 OctLuzern 07:320 min—
Sat 24 OctLuzern 07:320 min—
Fri 23 OctLuzern 07:33+1 min—
Thu 22 OctLuzern 07:330 min—
Wed 21 OctLuzern 07:34+2 min+2 min
Tue 20 OctLuzern 07:34+1 min+1 min
Mon 19 OctLuzern 07:41+9 min+9 min
Sun 18 OctLuzern 07:320 min—
Sat 17 OctLuzern 07:330 min—
Fri 16 OctLuzern 07:34+2 min+2 min
Thu 15 OctLuzern 07:320 min—