S4 21453 Wolfenschiessen – Luzern

View line S4

Wolfenschiessen 14:01 → Luzern 14:31 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 14:01 from Wolfenschiessen · Thu 5 Nov

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

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

  • Early 0% · 0
  • On time 100% · 38
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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