S4 21433 Wolfenschiessen – Luzern

View line S4

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

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 18:01 from Wolfenschiessen · Fri 13 Nov

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

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

  • Early 2% · 1
  • On time 98% · 42
  • 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=7
  • 100% W n=7
  • 100% T n=6
  • 100% F n=5
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

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