S4 21481 Wolfenschiessen – Luzern

View line S4

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

✓ Today’s run finished

Today it reached Luzern at 21:31 −1 min

  1. Wolfenschiessen21:01
  2. Stans21:09
  3. Stansstad21:13
  4. Hergiswil Matt21:20
  5. Horw21:23
  6. Luzern Allmend/Messe21:27
  7. Luzern21:31

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

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

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

  • Early 2% · 1
  • On time 98% · 47
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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