S4 21461 Wolfenschiessen – Luzern

View line S4

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

It has not run yet today

Last recorded run: Thursday 5 November +1 min

Next service: today 16:01 from Wolfenschiessen · Fri 6 Nov

Next departure 16:01 today · Wolfenschiessen
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
93%
39/42 runs under 3 min
RT coverage: 42 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Thu 3 Sept Max en route +8 min · last fix heading to Luzern +8 min
  • Fri 9 Oct Max en route +5 min · last fix heading to Luzern +5 min
  • Tue 6 Oct Max en route +3 min · last fix heading to Luzern +3 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 88% · 37
  • 3–10 min 7% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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