S44 22412 Luzern – Stans

View line S44

Luzern 17:38 → Stans 17:55 Mon, Tue, Wed, Thu, Fri 0 h 17 min · 4 stops zb Zentralbahn

✓ Today’s run finished

Today it reached Stans at 17:57 +2 min

  1. Luzern17:38
  2. Hergiswil NW17:46
  3. Stansstad17:51
  4. Stans17:55

Next service: tomorrow 17:38 from Luzern · Fri 13 Nov

Next departure 17:38 tomorrow · Luzern
On-time · 30 days
81%
17/21 runs under 3 min
RT coverage: 19 full · 2 partial · 1 no data
On-time · 90 days
86%
24/28 runs under 3 min
RT coverage: 26 full · 2 partial · 1 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

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

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

Worst days

  • Mon 2 Nov Max en route +4 min · last fix heading to Stans +4 min
  • Thu 22 Oct Max en route +4 min · last fix heading to Stans +4 min
  • Tue 27 Oct Max en route +4 min · last fix heading to Stans +4 min
  • Wed 21 Oct Max en route +3 min · last fix heading to Stans +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 24
  • 3–10 min 14% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 83% T n=6
  • 83% W n=6
  • 83% T n=6
  • 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
17:38on time on time
17:46 / 17:47≈ on time ≈ +2 min
17:51≈ +1 min ≈ +3 min
17:55+1 min +4 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 12 NovStans 17:57+2 min+2 min
Wed 11 NovStans 17:540 min—
Tue 10 NovStans 17:54−1 min—
Mon 9 NovStans 17:57+1 min+1 min
Fri 6 NovStans 17:540 min—
Thu 5 NovStans 17:57+1 min+1 min
Wed 4 NovStans 17:570 min—
Tue 3 NovStans 17:59+3 min+3 min
Mon 2 NovStans 17:59+4 min+4 min
Fri 30 OctStans 17:57+1 min—
Thu 29 OctStans 17:560 min—
Wed 28 OctStans 17:56+1 min+1 min
Tue 27 OctStans 18:00+4 min+4 min
Mon 26 OctStans 17:56No data—
Fri 23 OctStans 17:57+1 min—
Thu 22 OctStans 18:00+4 min+4 min
Wed 21 OctStans 17:59+3 min+3 min
Tue 20 OctStans 17:57+1 min+1 min
Mon 19 OctStans 17:57+1 min—
Fri 16 OctStansstad 17:53Partial coverage+1 min—
Thu 15 OctStansstad 17:53Partial coverage+1 min—
Wed 14 OctStansstad 17:53+1 min+1 min
Tue 13 OctStansstad 17:520 min—
Mon 12 OctStansstad 17:520 min—
Fri 9 OctStansstad 17:530 min—
Thu 8 OctStansstad 17:54+1 min+1 min
Wed 7 OctStansstad 17:530 min—
Tue 6 OctStansstad 17:54+2 min+2 min
Mon 5 OctStansstad 17:53+1 min—