S6 21657 Wolhusen → Luzern

View line S6

Wolhusen 16:19 → Luzern 16:43 Daily 0 h 24 min · 6 stops BLS

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

✓ Today’s run finished

Today it reached Luzern at 16:46 +3 min

  1. Wolhusen16:19
  2. Werthenstein16:21
  3. Schachen LU16:25
  4. Malters16:30
  5. Luzern Littau16:35
  6. Luzern16:43

Next service: tomorrow 16:19 from Wolhusen · Mon 23 Nov

Next departure 16:19 tomorrow · Wolhusen
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
56/57 runs under 3 min
RT coverage: 57 full · 0 partial · 0 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: +2 min

Last 30 days

Arrival delay at Luzern, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 22 Nov Max en route +3 min · last fix heading to Luzern +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 56
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=8
  • 100% W n=7
  • 100% T n=8
  • 100% F n=10
  • 100% S n=8
  • 89% S n=9

Stops and timetable

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

Last 90 days, 57 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
16:19+1 min +1 min
16:21≈ on time ≈ +1 min
16:25≈ on time ≈ +1 min
16:30 / 16:31≈ on time ≈ +1 min
16:35≈ on time ≈ +1 min
16:43on 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 NovLuzern 16:47+3 min+3 min
Sat 21 NovLuzern 16:44+2 min+2 min
Fri 20 NovLuzern 16:440 min—
Thu 19 NovLuzern 16:44+1 min—
Wed 18 NovLuzern 16:44+1 min—
Tue 17 NovLuzern 16:440 min—
Mon 16 NovLuzern 16:430 min—
Sun 15 NovLuzern 16:44+1 min+1 min
Sat 14 NovLuzern 16:440 min—
Fri 13 NovLuzern 16:440 min—
Thu 12 NovLuzern 16:430 min—
Wed 11 NovLuzern 16:440 min—
Tue 10 NovLuzern 16:44+1 min—
Mon 9 NovLuzern 16:44+1 min—
Sun 8 NovLuzern 16:440 min—
Sat 7 NovLuzern 16:44+1 min+1 min
Fri 6 NovLuzern 16:440 min—
Thu 5 NovLuzern 16:440 min—
Wed 4 NovLuzern 16:440 min—
Tue 3 NovLuzern 16:440 min—
Mon 2 NovLuzern 16:44+1 min—
Sun 1 NovLuzern 16:46+3 min+3 min
Sat 31 OctLuzern 16:440 min—
Fri 30 OctLuzern 16:45+1 min—
Thu 29 OctLuzern 16:45+1 min—
Wed 28 OctLuzern 16:440 min—
Tue 27 OctLuzern 16:440 min—
Mon 26 OctLuzern 16:440 min—
Sun 25 OctLuzern 16:440 min+1 min
Sat 24 OctLuzern 16:46+2 min+2 min