S4 21485 Wolfenschiessen – Luzern

View line S4

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

It has not run yet today

Last recorded run: Wednesday 11 November 0 min

Next service: today 21:01 from Wolfenschiessen · Thu 12 Nov

Next departure 21:01 today · Wolfenschiessen
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%
42/42 runs under 3 min
RT coverage: 42 full · 0 partial · 1 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: +2 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

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

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

On-time by weekday

  • 100% M n=7
  • 100% T n=5
  • 100% W n=6
  • 100% T n=5
  • 100% F n=5
  • 100% S n=7
  • 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
21:01on time on time
21:04≈ on time ≈ on time
21:09 / 21:10≈ on time ≈ on time
21:13 / 21:14≈ on time ≈ +1 min
21:17 / 21:18≈ on time ≈ +1 min
21:20≈ on time ≈ +1 min
21:23≈ on time ≈ +1 min
21:25≈ on time ≈ +1 min
21:27≈ on time ≈ +1 min
21: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
Wed 11 NovLuzern 22:320 min—
Tue 10 NovLuzern 22:320 min—
Mon 9 NovLuzern 22:32−1 min—
Sun 8 NovLuzern 22:320 min—
Sat 7 NovLuzern 22:290 min—
Fri 6 NovLuzern 22:34+1 min+1 min
Thu 5 NovLuzern 22:290 min—
Wed 4 NovLuzern 22:320 min—
Tue 3 NovLuzern 22:320 min—
Mon 2 NovLuzern 22:330 min—
Sun 1 NovLuzern 22:32−1 min—
Sat 31 OctLuzern 22:34+2 min+2 min
Fri 30 OctLuzern 22:33+1 min+1 min
Thu 29 OctLuzern 22:320 min—
Wed 28 OctLuzern 22:320 min—
Tue 27 OctLuzern 22:320 min—
Mon 26 OctLuzern 22:320 min—
Sun 25 OctLuzern 22:310 min—
Sat 24 OctLuzern 22:310 min—
Fri 23 OctLuzern 22:35+3 min+3 min
Thu 22 OctLuzern 22:320 min—
Wed 21 OctLuzern 22:35+3 min+3 min
Tue 20 OctLuzern 22:320 min—
Mon 19 OctLuzern 22:31−1 min—
Sun 18 OctLuzern 22:32−1 min—
Sat 17 OctLuzern 22:31−1 min—
Fri 16 OctLuzern 22:34+2 min+2 min
Thu 15 OctLuzern 22:320 min—
Wed 14 OctLuzern 22:320 min—
Tue 13 OctLuzern 22:32−1 min—