S6 21624 Luzern – Wolhusen

View line S6

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

✓ Today’s run finished

Today it reached Wolhusen at 07:41 +1 min

  1. Luzern07:16
  2. Luzern Littau07:22
  3. Malters07:28
  4. Schachen LU07:32
  5. Werthenstein07:36
  6. Wolhusen07:40

Next service: tomorrow 07:16 from Luzern · Sat 21 Nov

Next departure 07:16 tomorrow · Luzern
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
48/48 runs under 3 min
RT coverage: 48 full · 0 partial · 1 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

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

  • Early 0% · 0
  • On time 100% · 48
  • 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=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

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