S6 21692 Luzern – Wolhusen

View line S6

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

✓ Today’s run finished

Today it reached Wolhusen at 00:40 0 min

  1. Luzern00:16
  2. Luzern Littau00:22
  3. Malters00:28
  4. Schachen LU00:32
  5. Werthenstein00:36
  6. Wolhusen00:40

Next service: tomorrow 00:16 from Luzern · Sun 8 Nov

Next departure 00:16 tomorrow · Luzern
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 24 full · 0 partial · 1 no data
On-time · 90 days
98%
44/45 runs under 3 min
RT coverage: 45 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 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

Worst days

  • Fri 9 Oct Max en route +3 min · last fix heading to Wolhusen +3 min

Distribution · 90 days

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

  • Early 24% · 11
  • On time 73% · 33
  • 3–10 min 2% · 1
  • 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=7
  • 83% F n=6
  • 100% S n=5
  • 100% S n=7

Stops and timetable

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

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