S4 21493 Wolfenschiessen – Luzern

View line S4

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

✓ Today’s run finished

Today it reached Luzern at 00:31 0 min

  1. Wolfenschiessen00:01
  2. Stans00:09
  3. Stansstad00:13
  4. Hergiswil Matt00:20
  5. Horw00:23
  6. Luzern Allmend/Messe00:27
  7. Luzern00:31

Next service: tomorrow 00:01 from Wolfenschiessen · Fri 20 Nov

Next departure 00:01 tomorrow · Wolfenschiessen
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
94%
45/48 runs under 3 min
RT coverage: 48 full · 0 partial · 2 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 13 Oct Max en route +5 min · last fix heading to Luzern +5 min
  • Mon 12 Oct Max en route +5 min · last fix heading to Luzern +5 min
  • Tue 10 Nov Max en route +3 min · last fix heading to Luzern +3 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 90% · 43
  • 3–10 min 6% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 67% T n=6
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 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, 48 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:01on time on time
00:04≈ on time ≈ on time
00:09 / 00:10≈ on time ≈ on time
00:13 / 00:14≈ on time ≈ +1 min
00:17 / 00:18≈ on time ≈ +1 min
00:20≈ on time ≈ +1 min
00:23≈ on time ≈ +1 min
00:25≈ on time ≈ +1 min
00:27≈ on time ≈ +1 min
00:31on 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
Thu 19 NovLuzern 00:320 min—
Wed 18 NovLuzern 00:320 min—
Tue 17 NovLuzern 00:320 min—
Mon 16 NovLuzern 00:33+1 min+1 min
Sun 15 NovLuzern 00:34+2 min+2 min
Sat 14 NovLuzern 00:320 min—
Fri 13 NovLuzern 00:29−1 min—
Thu 12 NovLuzern 00:290 min—
Wed 11 NovLuzern 00:330 min—
Tue 10 NovLuzern 00:35+3 min+3 min
Mon 9 NovLuzern 00:320 min—
Sun 8 NovLuzern 00:290 min—
Sat 7 NovLuzern 00:320 min—
Fri 6 NovLuzern 00:29−1 min—
Thu 5 NovLuzern 00:29−1 min—
Wed 4 NovLuzern 00:320 min—
Tue 3 NovLuzern 00:32No data—
Mon 2 NovLuzern 00:330 min—
Sun 1 NovLuzern 00:31−1 min—
Sat 31 OctLuzern 00:31−1 min—
Fri 30 OctLuzern 00:31−1 min—
Thu 29 OctLuzern 00:320 min—
Wed 28 OctLuzern 00:320 min—
Tue 27 OctLuzern 00:320 min—
Mon 26 OctLuzern 00:33+2 min+2 min
Sun 25 OctLuzern 00:33+1 min—
Sat 24 OctLuzern 00:31−1 min—
Fri 23 OctLuzern 00:31−1 min—
Thu 22 OctLuzern 00:320 min—
Wed 21 OctLuzern 00:31−1 min—