S6 21624 Luzern – Wolhusen

View line S6

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

✓ Today’s run finished

Today it reached Wolhusen at 23:40 0 min

  1. Luzern23:16
  2. Luzern Littau23:22
  3. Malters23:28
  4. Schachen LU23:32
  5. Werthenstein23:36
  6. Wolhusen23:40

Next service: tomorrow 23:16 from Luzern · Fri 6 Nov

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

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

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

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 33 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 ≈ +1 min
23:36≈ on time ≈ +1 min
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
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—
Wed 21 OctWolhusen 07:410 min—
Tue 20 OctWolhusen 07:43+1 min+1 min
Mon 19 OctWolhusen 07:42+1 min+1 min
Sun 18 OctWolhusen 07:41−1 min—
Sat 17 OctWolhusen 07:41No data—
Fri 16 OctWolhusen 07:40−1 min—
Thu 15 OctWolhusen 07:42+1 min+1 min
Wed 14 OctWolhusen 07:410 min—
Tue 13 OctWolhusen 07:420 min—
Mon 12 OctWolhusen 07:410 min—
Sun 11 OctWolhusen 07:41+1 min—
Sat 10 OctWolhusen 07:420 min—
Fri 9 OctWolhusen 07:410 min—
Thu 8 OctWolhusen 07:43+2 min+2 min
Wed 7 OctWolhusen 07:410 min—