S4 21441 Wolfenschiessen – Luzern

View line S4

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

✓ Today’s run finished

Today, last fix heading to Luzern at 11:32 No data

  1. Wolfenschiessen11:01
  2. Stans11:09
  3. Stansstad11:13
  4. Hergiswil Matt11:20
  5. Horw11:23
  6. Luzern Allmend/Messe11:27
  7. Luzern11:31

Next service: tomorrow 11:01 from Wolfenschiessen · Tue 10 Nov

Next departure 11:01 tomorrow · Wolfenschiessen
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
100%
41/41 runs under 3 min
RT coverage: 41 full · 0 partial · 7 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

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

  • Early 5% · 2
  • On time 95% · 39
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=7
  • 100% T n=4
  • 100% F n=7
  • 100% S n=7
  • 100% S n=8

Stops and timetable

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

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