S4 21486 Luzern – Wolfenschiessen

View line S4

Luzern 20:27 → Wolfenschiessen 20:57 Daily 0 h 30 min · 10 stops SBB CFF FFS

It has not run yet today

Last recorded run: Wednesday 4 November −1 min

Next service: today 20:27 from Luzern · Thu 5 Nov

Next departure 20:27 today · Luzern
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
100%
37/37 runs under 3 min
RT coverage: 37 full · 0 partial · 1 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
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

Distribution · 90 days

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

  • Early 16% · 6
  • On time 84% · 31
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=6
  • 100% T n=5
  • 100% F n=5
  • 100% S n=5
  • 100% S n=6

Stops and timetable

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

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