S6 21685 Wolhusen – Luzern

View line S6

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

It has not run yet today

Last recorded run: Thursday 5 November −1 min

Next service: today 23:19 from Wolhusen · Fri 6 Nov

Next departure 23:19 today · Wolhusen
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 0 no data
On-time · 90 days
100%
50/50 runs under 3 min
RT coverage: 50 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: +1 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=7
  • 100% T n=5
  • 100% F n=7
  • 100% S n=9
  • 100% S n=9

Stops and timetable

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

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