S44 22406 Luzern – Stans

View line S44

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

✓ Today’s run finished

Today it reached Stans at 07:55 0 min

  1. Luzern07:38
  2. Hergiswil NW07:46
  3. Stansstad07:51
  4. Stans07:55

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

Next departure 07:38 tomorrow · Luzern
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
90%
26/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Tue 10 Nov Max en route +6 min · last fix heading to Stans +6 min
  • Mon 19 Oct Max en route +3 min · last fix heading to Stans +3 min
  • Thu 15 Oct Max en route +3 min · last fix heading to Stansstad +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 26
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 83% T n=6
  • 100% 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, 29 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:38on time on time
07:46 / 07:47≈ on time ≈ +1 min
07:51≈ +1 min ≈ +2 min
07:55+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
Thu 12 NovStans 07:570 min—
Wed 11 NovStans 07:57+1 min+1 min
Tue 10 NovStans 08:02+6 min+6 min
Mon 9 NovStans 07:540 min—
Fri 6 NovStans 07:58+2 min+2 min
Thu 5 NovStans 07:57+1 min—
Wed 4 NovStans 07:570 min—
Tue 3 NovStans 07:58+2 min+2 min
Mon 2 NovStans 07:59+2 min+2 min
Fri 30 OctStans 07:57+1 min+1 min
Thu 29 OctStans 07:58+1 min+1 min
Wed 28 OctStans 07:57+1 min—
Tue 27 OctStans 07:58+2 min+2 min
Mon 26 OctStans 07:57+1 min—
Fri 23 OctStans 07:57+1 min—
Thu 22 OctStans 07:58+2 min+2 min
Wed 21 OctStans 07:57+1 min+1 min
Tue 20 OctStans 07:59+2 min+2 min
Mon 19 OctStans 07:59+3 min+3 min
Fri 16 OctStansstad 07:510 min—
Thu 15 OctStansstad 07:55+3 min+3 min
Wed 14 OctStansstad 07:53+1 min—
Tue 13 OctStansstad 07:53+1 min—
Mon 12 OctStansstad 07:53+1 min—
Fri 9 OctStansstad 07:520 min—
Thu 8 OctStansstad 07:53+1 min—
Wed 7 OctStansstad 07:52+1 min—
Tue 6 OctStansstad 07:520 min—
Mon 5 OctStansstad 07:530 min—