S6 21688 Luzern – Wolhusen

View line S6

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

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 23:16 from Luzern · Thu 19 Nov

Next departure 23:16 today · Luzern
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 2 no data
On-time · 90 days
100%
50/50 runs under 3 min
RT coverage: 50 full · 0 partial · 2 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 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

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

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

Stops and timetable

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

Last 90 days, 50 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
23:16on time on time
23:22≈ on time ≈ on time
23:28 / 23:29≈ on time ≈ on time
23:32≈ on time ≈ on time
23:36≈ on time ≈ on time
23:40on 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 18 NovWolhusen 23:390 min—
Tue 17 NovWolhusen 23:390 min—
Mon 16 NovWolhusen 23:39No data—
Sun 15 NovMalters 23:29+1 min—
Sat 14 NovMalters 23:29+1 min—
Fri 13 NovWolhusen 23:390 min—
Thu 12 NovWolhusen 23:400 min—
Wed 11 NovWolhusen 23:390 min—
Tue 10 NovWolhusen 23:390 min—
Mon 9 NovWolhusen 23:390 min—
Sun 8 NovWolhusen 23:43+2 min+2 min
Sat 7 NovWolhusen 23:43+2 min+2 min
Fri 6 NovWolhusen 23:42+1 min—
Thu 5 NovWolhusen 23:390 min—
Wed 4 NovWolhusen 23:390 min—
Tue 3 NovWolhusen 23:390 min—
Mon 2 NovWolhusen 23:420 min—
Sun 1 NovWolhusen 23:42+1 min—
Sat 31 OctWolhusen 23:410 min—
Fri 30 OctWolhusen 23:410 min—
Thu 29 OctWolhusen 23:410 min—
Wed 28 OctWolhusen 23:410 min—
Tue 27 OctWolhusen 23:410 min—
Mon 26 OctWolhusen 23:420 min—
Sun 25 OctWolhusen 23:41No data—
Sat 24 OctWolhusen 23:40−1 min—
Fri 23 OctWolhusen 23:410 min—
Thu 22 OctWolhusen 23:420 min—
Wed 21 OctWolhusen 23:41+1 min—
Tue 20 OctWolhusen 23:410 min—