S4 21445 Wolfenschiessen – Luzern

View line S4

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

✓ Today’s run finished

Today it reached Luzern at 12:31 0 min

  1. Wolfenschiessen12:01
  2. Stans12:09
  3. Stansstad12:13
  4. Hergiswil Matt12:20
  5. Horw12:23
  6. Luzern Allmend/Messe12:27
  7. Luzern12:31

Next service: tomorrow 12:01 from Wolfenschiessen · Thu 12 Nov

Next departure 12:01 tomorrow · Wolfenschiessen
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
97%
35/36 runs under 3 min
RT coverage: 36 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

Worst days

  • Sun 25 Oct Max en route +4 min · last fix heading to Luzern +4 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 94% · 34
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=7
  • 100% W n=7
  • 100% T n=2
  • 100% F n=5
  • 100% S n=5
  • 83% S n=6

Stops and timetable

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

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