S1 21174 Sursee – Luzern

View line S1

Sursee 19:48 → Luzern 20:15 Daily 0 h 27 min · 9 stops SBB CFF FFS

It has not run yet today

Last recorded run: Sunday 8 November −1 min

Next service: today 19:48 from Sursee · Mon 9 Nov

Next departure 19:48 today · Sursee
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
98%
40/41 runs under 3 min
RT coverage: 41 full · 0 partial · 0 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: +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

  • Fri 23 Oct Max en route +8 min · last fix heading to Baar +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 40
  • 3–10 min 2% · 1
  • 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
  • 83% F n=6
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

Last 90 days, 41 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
19:48+1 min +1 min
19:50≈ +1 min ≈ +1 min
19:52≈ +1 min ≈ +1 min
19:57≈ +1 min ≈ +1 min
20:01≈ +1 min ≈ +1 min
20:03≈ +1 min ≈ +2 min
20:06≈ +1 min ≈ +2 min
20:08≈ +1 min ≈ +2 min
20:15+1 min +3 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
Sun 8 NovLuzern 21:14−1 min—
Sat 7 NovLuzern 21:140 min—
Fri 6 NovBaar 21:59+1 min+1 min
Thu 5 NovBaar 21:59+2 min+2 min
Wed 4 NovBaar 21:59+1 min—
Tue 3 NovBaar 21:59+1 min+1 min
Mon 2 NovBaar 21:59+1 min+1 min
Sun 1 NovBaar 21:590 min—
Sat 31 OctBaar 22:01+3 min+3 min
Fri 30 OctBaar 21:59+1 min+1 min
Thu 29 OctBaar 22:00+2 min+2 min
Wed 28 OctBaar 22:00+2 min+2 min
Tue 27 OctBaar 22:00+2 min+2 min
Mon 26 OctBaar 21:580 min—
Sun 25 OctBaar 22:00+2 min+4 min
Sat 24 OctBaar 22:00+3 min+3 min
Fri 23 OctBaar 22:06+8 min+8 min
Thu 22 OctBaar 21:59+1 min+1 min
Wed 21 OctBaar 21:59+1 min—
Tue 20 OctBaar 22:01+3 min+3 min
Mon 19 OctBaar 21:59+1 min+1 min
Sun 18 OctBaar 21:580 min—
Sat 17 OctBaar 21:59+1 min—
Fri 16 OctBaar 21:59+1 min—
Thu 15 OctBaar 21:57−1 min—
Wed 14 OctBaar 22:00+1 min+1 min
Tue 13 OctBaar 22:00+2 min+2 min
Mon 12 OctBaar 21:59+1 min+1 min
Sun 11 OctBaar 21:59+2 min+2 min
Sat 10 OctBaar 21:580 min—