S41 22436 Luzern – Horw

View line S41

Luzern 08:19 → Horw 08:26 Mon, Tue, Wed, Thu, Fri 0 h 07 min · 4 stops zb Zentralbahn

✓ Today’s run finished

Today it reached Horw at 08:26 0 min

  1. Luzern08:19
  2. Luzern Allmend/Messe08:21
  3. Kriens Mattenhof08:23
  4. Horw08:26

Next service: tomorrow 08:19 from Luzern · Fri 13 Nov

Next departure 08:19 tomorrow · Luzern
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 1 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

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

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

Worst days

  • Tue 10 Nov Max en route +3 min · last fix heading to Horw +3 min

Distribution · 90 days

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

  • Early 7% · 2
  • On time 89% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 83% T n=6
  • 100% W n=6
  • 100% T n=5
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 28 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
08:19on time on time
08:21≈ on time ≈ on time
08:23≈ on time ≈ on time
08:26on 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
Thu 12 NovHorw 08:240 min—
Wed 11 NovHorw 08:270 min—
Tue 10 NovHorw 08:29+3 min+3 min
Mon 9 NovHorw 08:240 min—
Fri 6 NovHorw 08:27−1 min—
Thu 5 NovHorw 08:270 min—
Wed 4 NovHorw 08:27−1 min—
Tue 3 NovHorw 08:270 min—
Mon 2 NovHorw 08:280 min—
Fri 30 OctHorw 08:26−1 min—
Thu 29 OctHorw 08:27−1 min—
Wed 28 OctHorw 08:260 min—
Tue 27 OctHorw 08:270 min—
Mon 26 OctHorw 08:270 min—
Fri 23 OctHorw 08:270 min—
Thu 22 OctHorw 08:270 min—
Wed 21 OctHorw 08:270 min—
Tue 20 OctHorw 08:270 min—
Mon 19 OctHorw 08:26−1 min—
Fri 16 OctHorw 08:270 min—
Thu 15 OctHorw 08:27No data—
Wed 14 OctHorw 08:26−1 min—
Tue 13 OctHorw 08:280 min—
Mon 12 OctHorw 08:270 min—
Fri 9 OctHorw 08:270 min—
Thu 8 OctHorw 08:270 min—
Wed 7 OctHorw 08:28+1 min+1 min
Tue 6 OctHorw 08:270 min—
Mon 5 OctHorw 08:27−1 min—