S6 21665 Wolhusen – Luzern

View line S6

Wolhusen 09:19 → Luzern 09:43 Daily 0 h 24 min · 6 stops SBB CFF FFS

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: tomorrow 09:19 from Wolhusen · Fri 6 Nov

Next departure 09:19 tomorrow · Wolhusen
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
97%
35/36 runs under 3 min
RT coverage: 36 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

Worst days

  • Fri 16 Oct Max en route +3 min · last fix heading to Luzern +3 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 94% · 34
  • 3–10 min 3% · 1
  • 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=4
  • 75% F n=4
  • 100% S n=4
  • 100% S n=6

Stops and timetable

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

Last 90 days, 36 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
09:19+1 min +1 min
09:21≈ +1 min ≈ +1 min
09:25≈ +1 min ≈ +1 min
09:30 / 09:31≈ +1 min ≈ +1 min
09:35≈ +1 min ≈ +2 min
09:43+1 min +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 4 NovLuzern 18:44+1 min+1 min
Tue 3 NovLuzern 18:440 min—
Mon 2 NovLuzern 18:440 min—
Sun 1 NovLuzern 18:44+1 min—
Sat 31 OctLuzern 18:440 min—
Fri 30 OctLuzern 18:45+1 min—
Thu 29 OctLuzern 18:45+1 min—
Wed 28 OctLuzern 18:45+1 min+1 min
Tue 27 OctLuzern 18:46+2 min+2 min
Mon 26 OctLuzern 18:45+1 min—
Sun 25 OctLuzern 18:46+2 min+2 min
Sat 24 OctLuzern 18:45+1 min+1 min
Fri 23 OctLuzern 18:45+1 min—
Thu 22 OctLuzern 18:47+2 min+2 min
Wed 21 OctLuzern 18:45+1 min+1 min
Tue 20 OctLuzern 18:47+3 min+3 min
Mon 19 OctLuzern 18:46+2 min+2 min
Sun 18 OctLuzern 18:440 min—
Sat 17 OctLuzern 18:440 min—
Fri 16 OctLuzern 18:48+3 min+3 min
Thu 15 OctLuzern 18:45+1 min+1 min
Wed 14 OctLuzern 18:45+2 min+2 min
Tue 13 OctLuzern 18:45+1 min—
Mon 12 OctLuzern 18:45+2 min+2 min
Sun 11 OctLuzern 18:440 min—
Sat 10 OctLuzern 18:440 min—
Fri 9 OctLuzern 18:450 min—
Thu 8 OctLuzern 18:46+2 min+2 min
Wed 7 OctLuzern 18:440 min—
Tue 6 OctLuzern 18:47+3 min+3 min