S4 21494 Luzern – Wolfenschiessen

View line S4

Luzern 00:32 → Wolfenschiessen 01:03 Daily 0 h 31 min · 10 stops zb Zentralbahn

✓ Today’s run finished

Today it reached Wolfenschiessen at 01:03 −1 min

  1. Luzern00:32
  2. Kriens Mattenhof00:36
  3. Horw00:38
  4. Hergiswil NW00:44
  5. Stansstad00:48
  6. Dallenwil00:59
  7. Wolfenschiessen01:03

Next service: tomorrow 00:32 from Luzern · Sat 7 Nov

Next departure 00:32 tomorrow · Luzern
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%
45/46 runs under 3 min
RT coverage: 46 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Wolfenschiessen, 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 +3 min · last fix heading to Wolfenschiessen +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 46 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
00:32on time on time
00:34≈ on time ≈ on time
00:36≈ on time ≈ on time
00:38≈ on time ≈ on time
00:41≈ on time ≈ on time
00:44 / 00:45≈ on time ≈ on time
00:48 / 00:50≈ on time ≈ +1 min
00:54≈ on time ≈ +1 min
00:59≈ on time ≈ +1 min
01:03+1 min +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 NovWolfenschiessen 01:02−1 min—
Thu 5 NovWolfenschiessen 01:03−1 min—
Wed 4 NovWolfenschiessen 01:04+1 min+1 min
Tue 3 NovWolfenschiessen 01:040 min—
Mon 2 NovWolfenschiessen 01:04−1 min+2 min
Sun 1 NovWolfenschiessen 01:04+1 min+2 min
Sat 31 OctWolfenschiessen 01:040 min+2 min
Fri 30 OctWolfenschiessen 01:03−1 min+2 min
Thu 29 OctWolfenschiessen 01:05+1 min+2 min
Wed 28 OctWolfenschiessen 01:06+2 min+2 min
Tue 27 OctWolfenschiessen 01:06+1 min+1 min
Mon 26 OctWolfenschiessen 01:06+1 min+1 min
Sun 25 OctWolfenschiessen 01:05+3 min+3 min
Sat 24 OctWolfenschiessen 01:07+3 min+3 min
Fri 23 OctWolfenschiessen 01:04+1 min+2 min
Thu 22 OctWolfenschiessen 01:040 min—
Wed 21 OctWolfenschiessen 01:05+1 min+2 min
Tue 20 OctWolfenschiessen 01:040 min+2 min
Mon 19 OctStansstad 00:50+1 min—
Sun 18 OctStansstad 00:50+1 min—
Sat 17 OctStansstad 00:500 min—
Fri 16 OctStansstad 00:50+1 min—
Thu 15 OctStansstad 00:50+1 min—
Wed 14 OctStansstad 00:490 min—
Tue 13 OctStansstad 00:49+1 min—
Mon 12 OctStansstad 00:49+1 min—
Sun 11 OctStansstad 00:500 min—
Sat 10 OctStansstad 00:50+1 min—
Fri 9 OctStansstad 00:500 min—
Thu 8 OctStansstad 00:500 min—