S1 21153 Luzern – Sursee

View line S1

Luzern 16:14 → Sursee 16:40 Daily 0 h 26 min · 9 stops SBB CFF FFS

It has not run yet today

Last recorded run: Sunday 8 November +1 min

Next service: today 16:14 from Luzern · Mon 9 Nov

Next departure 16:14 today · Luzern
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
95%
56/59 runs under 3 min
RT coverage: 59 full · 0 partial · 7 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: +2 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

  • Wed 4 Nov Max en route +4 min · last fix heading to Sursee +4 min
  • Thu 8 Oct Max en route +3 min · last fix heading to Sursee +3 min
  • Sat 17 Oct Max en route +3 min · last fix heading to Sursee +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 56
  • 3–10 min 5% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=8
  • 86% W n=7
  • 86% T n=7
  • 100% F n=8
  • 90% S n=10
  • 100% S n=12

Stops and timetable

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

Last 90 days, 59 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
16:14+1 min +1 min
16:19≈ +1 min ≈ +1 min
16:21 / 16:22≈ +1 min ≈ +1 min
16:24≈ +1 min ≈ +1 min
16:27≈ +1 min ≈ +1 min
16:31≈ +1 min ≈ +1 min
16:34≈ +1 min ≈ +2 min
16:37≈ +1 min ≈ +2 min
16:40+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
Sun 8 NovSursee 16:43+1 min+1 min
Sat 7 NovSursee 16:39+1 min—
Fri 6 NovSursee 16:43+2 min+2 min
Thu 5 NovSursee 16:42+1 min—
Wed 4 NovSursee 16:44+4 min+4 min
Tue 3 NovSursee 16:42+1 min+1 min
Mon 2 NovSursee 16:43+1 min+1 min
Sun 1 NovSursee 16:42+1 min—
Sat 31 OctSursee 16:42+1 min—
Fri 30 OctSursee 16:42+1 min—
Thu 29 OctSursee 16:42+1 min+1 min
Wed 28 OctSursee 16:42+1 min—
Tue 27 OctSursee 16:410 min—
Mon 26 OctSursee 16:43+1 min+1 min
Sun 25 OctSursee 16:42+2 min+2 min
Sat 24 OctSursee 16:43+2 min+2 min
Fri 23 OctSursee 16:42+1 min+1 min
Thu 22 OctSursee 16:43+2 min+2 min
Wed 21 OctSursee 16:43+2 min+2 min
Tue 20 OctSursee 16:420 min—
Mon 19 OctSursee 16:42+1 min+1 min
Sun 18 OctSursee 16:42+1 min+1 min
Sat 17 OctSursee 16:44+3 min+3 min
Fri 16 OctSursee 16:42+1 min—
Thu 15 OctSursee 16:43+2 min+2 min
Wed 14 OctSursee 16:43+2 min+2 min
Tue 13 OctSursee 16:43+1 min+1 min
Mon 12 OctSursee 16:410 min—
Sun 11 OctSursee 16:42+1 min—
Sat 10 OctSursee 16:42+1 min—