S44 22403 Stans – Luzern

View line S44

Stans 06:01 → Luzern 06:18 Mon, Tue, Wed, Thu, Fri 0 h 17 min · 4 stops zb Zentralbahn

✓ Today’s run finished

Today it reached Luzern at 06:19 +1 min

  1. Stans06:01
  2. Stansstad06:04
  3. Hergiswil NW06:08
  4. Luzern06:18

Next service: Monday 06:01 from Stans · Mon 23 Nov

Next departure 06:01 Monday · Stans
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
97%
38/39 runs under 3 min
RT coverage: 39 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Worst days

  • Tue 17 Nov Max en route +7 min · last fix heading to Luzern +7 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 95% · 37
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 88% T n=8
  • 100% W n=8
  • 100% T n=8
  • 100% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 39 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
06:01on time on time
06:04 / 06:05≈ on time ≈ on time
06:08 / 06:09≈ on time ≈ +1 min
06:18+1 min +2 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
Fri 20 NovLuzern 06:19+1 min—
Thu 19 NovLuzern 06:22+2 min+2 min
Wed 18 NovLuzern 06:19+1 min—
Tue 17 NovLuzern 06:24+7 min+7 min
Mon 16 NovLuzern 06:19+1 min—
Fri 13 NovLuzern 06:190 min—
Thu 12 NovLuzern 06:19+1 min—
Wed 11 NovLuzern 06:190 min—
Tue 10 NovLuzern 06:19+1 min—
Mon 9 NovLuzern 06:190 min—
Fri 6 NovLuzern 06:190 min—
Thu 5 NovLuzern 06:190 min—
Wed 4 NovLuzern 06:19−1 min—
Tue 3 NovLuzern 06:190 min—
Mon 2 NovLuzern 06:190 min—
Fri 30 OctLuzern 06:190 min—
Thu 29 OctLuzern 06:190 min—
Wed 28 OctLuzern 06:21+2 min+2 min
Tue 27 OctLuzern 06:20+1 min+1 min
Mon 26 OctLuzern 06:21+1 min+1 min
Fri 23 OctLuzern 06:20+1 min+1 min
Thu 22 OctLuzern 06:200 min—
Wed 21 OctLuzern 06:21+2 min+2 min
Tue 20 OctLuzern 06:19+1 min—
Mon 19 OctLuzern 06:21+2 min+2 min
Fri 16 OctLuzern 06:20+1 min+1 min
Thu 15 OctLuzern 06:20+1 min—
Wed 14 OctLuzern 06:190 min—
Tue 13 OctLuzern 06:19+1 min—
Mon 12 OctLuzern 06:190 min—