S55 22525 Sachseln – Luzern

View line S55

Sachseln 07:04 → Luzern 07:36 Mon, Tue, Wed, Thu, Fri 0 h 32 min · 6 stops zb Zentralbahn

✓ Today’s run finished

Today it reached Luzern at 07:36 −1 min

  1. Sachseln07:04
  2. Sarnen07:07
  3. Sarnen Nord07:09
  4. Alpnach Dorf07:13
  5. Hergiswil NW07:22
  6. Luzern07:36

Next service: tomorrow 07:04 from Sachseln · Fri 6 Nov

Next departure 07:04 tomorrow · Sachseln
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 0 no data
Typical delay
−3min
Median at arrival, 90 days
30 days: −3 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

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

  • Early 81% · 22
  • On time 19% · 5
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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
07:04on time on time
07:07 / 07:08≈ on time ≈ on time
07:09≈ on time ≈ on time
07:13≈ 1 min early ≈ on time
07:22 / 07:24≈ 2 min early ≈ on time
07:363 min early 1 min early

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 07:34−1 min—
Wed 4 NovLuzern 07:34−3 min—
Tue 3 NovLuzern 07:34−3 min—
Mon 2 NovLuzern 07:34−1 min—
Fri 30 OctLuzern 07:34−3 min—
Thu 29 OctLuzern 07:35−3 min—
Wed 28 OctLuzern 07:370 min—
Tue 27 OctLuzern 07:35−3 min—
Mon 26 OctLuzern 07:37−1 min—
Fri 23 OctLuzern 07:34−3 min—
Thu 22 OctLuzern 07:35−3 min—
Wed 21 OctLuzern 07:37−1 min—
Tue 20 OctLuzern 07:35−2 min—
Mon 19 OctLuzern 07:34−3 min—
Fri 16 OctLuzern 07:36−1 min—
Thu 15 OctLuzern 07:34−3 min—
Wed 14 OctLuzern 07:35−2 min—
Tue 13 OctLuzern 07:36−2 min—
Mon 12 OctLuzern 07:33−3 min—
Fri 9 OctLuzern 07:34−3 min—
Thu 8 OctLuzern 07:35−2 min—
Wed 7 OctLuzern 07:34−3 min—
Tue 6 OctLuzern 07:34−3 min—
Mon 5 OctLuzern 07:35−2 min—
Thu 24 SeptLuzern 06:36−3 min—
Wed 23 SeptLuzern 06:35−3 min—
Tue 22 SeptLuzern 06:35−1 min—