S4 21492 Luzern – Wolfenschiessen

View line S4

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

It has not run yet today

Last recorded run: Saturday 14 November +1 min

Next service: today 23:57 from Luzern · Sun 15 Nov

Next departure 23:57 today · Luzern
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
On-time · 90 days
100%
47/47 runs under 3 min
RT coverage: 47 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 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

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

  • Early 15% · 7
  • On time 85% · 40
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 47 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
23:57on time on time
23:59≈ on time ≈ on time
00:01≈ on time ≈ on time
00:03≈ on time ≈ on time
00:06≈ on time ≈ on time
00:09 / 00:10≈ on time ≈ on time
00:13 / 00:14≈ on time ≈ +1 min
00:17 / 00:18≈ on time ≈ +1 min
00:22≈ on time ≈ +1 min
00:27on 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
Sat 14 NovWolfenschiessen 00:29+1 min+1 min
Fri 13 NovWolfenschiessen 00:270 min—
Thu 12 NovWolfenschiessen 00:28−1 min—
Wed 11 NovWolfenschiessen 00:27−1 min—
Tue 10 NovWolfenschiessen 00:27−1 min+4 min
Sun 8 NovWolfenschiessen 00:27−1 min—
Sat 7 NovWolfenschiessen 00:27−1 min—
Fri 6 NovWolfenschiessen 00:270 min—
Thu 5 NovWolfenschiessen 00:24−1 min—
Wed 4 NovWolfenschiessen 00:27−1 min—
Tue 3 NovWolfenschiessen 00:29+1 min+1 min
Mon 2 NovWolfenschiessen 00:28−1 min+2 min
Sun 1 NovWolfenschiessen 00:27−1 min—
Sat 31 OctWolfenschiessen 00:29+2 min+2 min
Fri 30 OctWolfenschiessen 00:27−1 min—
Thu 29 OctWolfenschiessen 00:27−1 min—
Wed 28 OctWolfenschiessen 00:280 min—
Tue 27 OctWolfenschiessen 00:29+1 min—
Mon 26 OctWolfenschiessen 00:29+1 min+1 min
Sun 25 OctWolfenschiessen 00:29+1 min+3 min
Sat 24 OctWolfenschiessen 00:28+1 min—
Fri 23 OctWolfenschiessen 00:29+1 min+1 min
Thu 22 OctWolfenschiessen 00:280 min—
Wed 21 OctWolfenschiessen 00:280 min—
Tue 20 OctWolfenschiessen 00:29+1 min—
Mon 19 OctWolfenschiessen 00:28+1 min—
Sun 18 OctStansstad 00:150 min—
Sat 17 OctStansstad 00:140 min—
Fri 16 OctStansstad 00:140 min—
Thu 15 OctStansstad 00:15+1 min—