S4 21418 Luzern → Wolfenschiessen

View line S4

Luzern 05:27 → Wolfenschiessen 05:57 Daily 0 h 30 min · 10 stops zb Zentralbahn

S4 21418 Luzern–Wolfenschiessen: final delay under 3 min on 29 of its 29 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 06:34 (GMT+1).

✓ Today’s run finished

Today it reached Wolfenschiessen at 05:57 0 min

  1. Luzern05:27
  2. Kriens Mattenhof05:31
  3. Horw05:33
  4. Hergiswil NW05:39
  5. Stansstad05:43
  6. Dallenwil05:52
  7. Wolfenschiessen05:57

Next service: tomorrow 05:27 from Luzern · Mon 23 Nov

Next departure 05:27 tomorrow · Luzern
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
98%
48/49 runs under 3 min
RT coverage: 49 full · 0 partial · 1 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 Wolfenschiessen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 19 Oct Max en route +4 min · last fix heading to Wolfenschiessen +4 min

Distribution · 90 days

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

  • Early 8% · 4
  • On time 90% · 44
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 100% S n=6
  • 100% S n=8

Stops and timetable

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

Last 90 days, 49 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
05:27on time +1 min
05:29≈ on time ≈ +1 min
05:31≈ on time ≈ +1 min
05:33≈ on time ≈ +1 min
05:36≈ on time ≈ +1 min
05:39 / 05:40≈ on time ≈ +1 min
05:43 / 05:44≈ on time ≈ +1 min
05:48≈ on time ≈ +1 min
05:52≈ on time ≈ +1 min
05:57on 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
Sun 22 NovWolfenschiessen 05:540 min—
Sat 21 NovWolfenschiessen 05:580 min+1 min
Fri 20 NovWolfenschiessen 05:57−1 min—
Thu 19 NovWolfenschiessen 05:590 min—
Wed 18 NovWolfenschiessen 05:590 min—
Tue 17 NovWolfenschiessen 05:59+1 min+1 min
Mon 16 NovWolfenschiessen 05:57−1 min—
Sun 15 NovWolfenschiessen 05:57−1 min—
Sat 14 NovWolfenschiessen 05:57−1 min—
Fri 13 NovWolfenschiessen 05:59+2 min+3 min
Thu 12 NovWolfenschiessen 05:570 min—
Wed 11 NovWolfenschiessen 05:58+1 min—
Tue 10 NovWolfenschiessen 05:59+1 min—
Mon 9 NovWolfenschiessen 05:570 min—
Sun 8 NovWolfenschiessen 05:57−1 min—
Sat 7 NovWolfenschiessen 05:57−1 min—
Fri 6 NovWolfenschiessen 05:570 min—
Thu 5 NovWolfenschiessen 05:580 min—
Wed 4 NovWolfenschiessen 05:58+1 min—
Tue 3 NovWolfenschiessen 05:58−1 min—
Mon 2 NovWolfenschiessen 05:57−1 min—
Sun 1 NovWolfenschiessen 06:01+3 min+3 min
Sat 31 OctWolfenschiessen 05:580 min—
Fri 30 OctWolfenschiessen 05:57−1 min—
Thu 29 OctWolfenschiessen 05:59+1 min—
Wed 28 OctWolfenschiessen 06:00+1 min+2 min
Tue 27 OctWolfenschiessen 05:580 min—
Mon 26 OctWolfenschiessen 05:580 min—
Sun 25 OctWolfenschiessen 05:570 min—
Sat 24 OctWolfenschiessen 05:58No data—