S6 21652 Luzern → Wolhusen

View line S6

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

S6 21652 Luzern–Wolhusen: final delay under 3 min on 21 of its 21 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 15:22 (GMT+1).

✓ Today’s run finished

Today it reached Wolhusen at 14:41 +1 min

  1. Luzern14:16
  2. Luzern Littau14:22
  3. Malters14:28
  4. Schachen LU14:32
  5. Werthenstein14:36
  6. Wolhusen14:40

Next service: tomorrow 14:16 from Luzern · Mon 23 Nov

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

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

  • Early 3% · 1
  • On time 97% · 36
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=7
  • 100% W n=7
  • 100% T n=1
  • 100% F n=7
  • 100% S n=6
  • 100% S n=8

Stops and timetable

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

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