S6 21616 Luzern – Wolhusen

View line S6

Luzern 05:16 → Wolhusen 05:40 Mon, Tue, Wed, Thu, Fri 0 h 24 min · 6 stops BLS

✓ Today’s run finished

Today it reached Wolhusen at 05:40 0 min

  1. Luzern05:16
  2. Luzern Littau05:22
  3. Malters05:28
  4. Schachen LU05:32
  5. Werthenstein05:36
  6. Wolhusen05:40

Next service: tomorrow 05:16 from Luzern · Tue 17 Nov

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

Distribution · 90 days

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

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

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
05:16on time on time
05:22≈ on time ≈ +1 min
05:28 / 05:29≈ on time ≈ +1 min
05:32≈ on time ≈ +1 min
05:36≈ on time ≈ +1 min
05: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
Mon 16 NovWolhusen 05:390 min—
Fri 13 NovWolhusen 05:400 min—
Thu 12 NovWolhusen 05:390 min—
Wed 11 NovWolhusen 05:42+1 min—
Tue 10 NovWolhusen 05:420 min—
Mon 9 NovWolhusen 05:390 min—
Fri 6 NovWolhusen 05:390 min—
Thu 5 NovWolhusen 05:390 min—
Wed 4 NovWolhusen 05:390 min—
Tue 3 NovWolhusen 05:390 min—
Mon 2 NovWolhusen 05:390 min—
Fri 30 OctWolhusen 05:410 min—
Thu 29 OctWolhusen 05:410 min—
Wed 28 OctWolhusen 05:410 min—
Tue 27 OctWolhusen 05:410 min—
Mon 26 OctWolhusen 05:400 min—
Fri 23 OctWolhusen 05:410 min—
Thu 22 OctWolhusen 05:42+1 min+1 min
Wed 21 OctWolhusen 05:410 min—
Tue 20 OctWolhusen 05:410 min—
Mon 19 OctWolhusen 05:410 min—
Fri 16 OctWolhusen 05:40−1 min—
Thu 15 OctWolhusen 05:43+2 min+2 min
Wed 14 OctWolhusen 05:410 min—
Tue 13 OctWolhusen 05:410 min—
Mon 12 OctWolhusen 05:40−1 min—
Fri 9 OctWolhusen 05:410 min—
Thu 8 OctWolhusen 05:420 min—
Wed 7 OctWolhusen 05:410 min—
Tue 6 OctWolhusen 05:41−1 min—