S1 21179 Luzern – Sursee

View line S1

Luzern 22:44 → Sursee 23:10 Daily 0 h 26 min · 9 stops SBB CFF FFS

It has not run yet today

Last recorded run: Monday 9 November +2 min

Next service: today 22:44 from Luzern · Tue 10 Nov

Next departure 22:44 today · Luzern
On-time · 30 days
86%
25/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
93%
65/70 runs under 3 min
RT coverage: 70 full · 0 partial · 9 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Sursee, 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 +6 min · last fix heading to Sursee +6 min
  • Sat 3 Oct Max en route +5 min · last fix heading to Sursee +5 min
  • Mon 2 Nov Max en route +4 min · last fix heading to Sursee +4 min
  • Thu 22 Oct Max en route +3 min · last fix heading to Sursee +3 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Sursee +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 65
  • 3–10 min 7% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 100% T n=8
  • 89% W n=9
  • 90% T n=10
  • 90% F n=10
  • 91% S n=11
  • 100% S n=13

Stops and timetable

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

Last 90 days, 70 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
22:44on time on time
22:49≈ on time ≈ +1 min
22:51 / 22:52≈ on time ≈ +1 min
22:54≈ on time ≈ +1 min
22:57≈ +1 min ≈ +1 min
23:01≈ +1 min ≈ +2 min
23:04≈ +1 min ≈ +2 min
23:07≈ +1 min ≈ +2 min
23:10+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
Mon 9 NovSursee 23:13+2 min+2 min
Sun 8 NovSursee 23:12+1 min—
Sat 7 NovSursee 23:12+2 min+2 min
Fri 6 NovSursee 23:14+3 min+3 min
Thu 5 NovSursee 23:12+1 min—
Wed 4 NovSursee 23:14+3 min+3 min
Tue 3 NovSursee 23:13+2 min+2 min
Mon 2 NovSursee 23:14+4 min+4 min
Sun 1 NovSursee 23:120 min—
Sat 31 OctSursee 23:12+1 min+1 min
Fri 30 OctSursee 23:13+2 min+2 min
Thu 29 OctSursee 23:12+1 min—
Wed 28 OctSursee 23:12+1 min+1 min
Tue 27 OctSursee 23:13+2 min+2 min
Mon 26 OctSursee 23:13+2 min+2 min
Sun 25 OctSursee 23:13+2 min+2 min
Sat 24 OctSursee 23:13+2 min+2 min
Fri 23 OctSursee 23:17+6 min+6 min
Thu 22 OctSursee 23:15+3 min+3 min
Wed 21 OctSursee 23:12+2 min+2 min
Tue 20 OctSursee 23:13+2 min+2 min
Mon 19 OctSursee 23:12+1 min—
Sun 18 OctSursee 23:120 min—
Sat 17 OctSursee 23:12+1 min+1 min
Fri 16 OctSursee 23:12+1 min—
Thu 15 OctSursee 23:11+1 min—
Wed 14 OctSursee 23:13+2 min+2 min
Tue 13 OctSursee 23:13+2 min+2 min
Mon 12 OctSursee 23:11+1 min+1 min
Sun 11 OctSursee 23:12+1 min—