S6 21676 Luzern – Wolhusen

View line S6

Luzern 20:16 → Wolhusen 20:40 Daily 0 h 24 min · 6 stops BLS

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 20:16 from Luzern · Wed 18 Nov

Next departure 20:16 today · Luzern
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%
58/58 runs under 3 min
RT coverage: 58 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Wolhusen, 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

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

  • Early 3% · 2
  • On time 97% · 56
  • 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=9
  • 100% W n=8
  • 100% T n=6
  • 100% F n=11
  • 100% S n=7
  • 100% S n=10

Stops and timetable

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

Last 90 days, 58 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
20:16on time on time
20:22≈ on time ≈ on time
20:28 / 20:29≈ on time ≈ on time
20:32≈ on time ≈ on time
20:36≈ on time ≈ on time
20:40on time on time

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
Tue 17 NovWolhusen 20:390 min—
Mon 16 NovWolhusen 20:39No data—
Sun 15 NovMalters 20:290 min—
Sat 14 NovMalters 20:290 min—
Fri 13 NovWolhusen 20:420 min—
Thu 12 NovWolhusen 20:420 min—
Wed 11 NovWolhusen 20:390 min—
Tue 10 NovWolhusen 20:390 min—
Mon 9 NovWolhusen 20:390 min—
Sun 8 NovWolhusen 20:390 min—
Sat 7 NovWolhusen 20:42+1 min+1 min
Fri 6 NovWolhusen 20:390 min—
Thu 5 NovWolhusen 20:390 min—
Wed 4 NovWolhusen 20:390 min—
Tue 3 NovWolhusen 20:390 min—
Mon 2 NovWolhusen 20:390 min—
Sun 1 NovWolhusen 20:420 min—
Sat 31 OctWolhusen 20:410 min—
Fri 30 OctWolhusen 20:410 min—
Thu 29 OctWolhusen 20:410 min—
Wed 28 OctWolhusen 20:410 min—
Tue 27 OctWolhusen 20:410 min—
Mon 26 OctWolhusen 20:420 min—
Sun 25 OctWolhusen 20:400 min—
Sat 24 OctWolhusen 20:410 min—
Fri 23 OctWolhusen 20:410 min—
Thu 22 OctWolhusen 20:40−1 min—
Wed 21 OctWolhusen 20:410 min—
Tue 20 OctWolhusen 20:410 min—
Mon 19 OctWolhusen 20:400 min—