S4 21437 Wolfenschiessen – Luzern

View line S4

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

✓ Today’s run finished

Today it reached Luzern at 10:31 0 min

  1. Wolfenschiessen10:01
  2. Stans10:09
  3. Stansstad10:13
  4. Hergiswil Matt10:20
  5. Horw10:23
  6. Luzern Allmend/Messe10:27
  7. Luzern10:31

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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 46
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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