S44 22411 Stans – Luzern

View line S44

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

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 17:01 from Stans · Wed 11 Nov

Next departure 17:01 today · Stans
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
94%
30/32 runs under 3 min
RT coverage: 32 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Wed 21 Oct Max en route +6 min · last fix heading to Luzern +6 min
  • Tue 27 Oct Max en route +3 min · last fix heading to Luzern +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 30
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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