S1 21144 Sursee – Luzern

View line S1

Sursee 13:18 → Luzern 13:45 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 13:18 from Sursee · Mon 9 Nov

Next departure 13:18 today · Sursee
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 8 no data
On-time · 90 days
100%
43/43 runs under 3 min
RT coverage: 43 full · 0 partial · 10 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=7
  • 100% W n=7
  • 100% T n=2
  • 100% F n=7
  • 100% S n=8
  • 100% S n=9

Stops and timetable

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

Last 90 days, 43 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
13:18on time on time
13:20≈ on time ≈ +1 min
13:22≈ on time ≈ +1 min
13:26 / 13:27≈ on time ≈ +1 min
13:31≈ on time ≈ +1 min
13:33≈ on time ≈ +1 min
13:36≈ on time ≈ +1 min
13:38≈ on time ≈ +2 min
13:45on time +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 NovLuzern 13:44−1 min—
Sat 7 NovLuzern 13:440 min—
Fri 6 NovBaar 14:280 min—
Thu 5 NovBaar 14:28No data—
Wed 4 NovBaar 14:29+1 min+1 min
Tue 3 NovBaar 14:29+1 min—
Mon 2 NovBaar 14:28No data—
Sun 1 NovBaar 14:29+1 min—
Sat 31 OctBaar 14:29+1 min—
Fri 30 OctBaar 14:280 min—
Thu 29 OctBaar 14:28No data—
Wed 28 OctBaar 14:31+2 min+2 min
Tue 27 OctBaar 14:280 min—
Mon 26 OctBaar 14:28No data—
Sun 25 OctBaar 14:29+1 min+1 min
Sat 24 OctBaar 14:280 min—
Fri 23 OctBaar 14:280 min—
Thu 22 OctBaar 14:28No data—
Wed 21 OctBaar 14:30+2 min+2 min
Tue 20 OctBaar 14:280 min—
Mon 19 OctBaar 14:28No data—
Sun 18 OctBaar 14:30+2 min+2 min
Sat 17 OctBaar 14:30+2 min+2 min
Fri 16 OctBaar 14:30+3 min+3 min
Thu 15 OctBaar 14:28No data—
Wed 14 OctBaar 14:280 min—
Tue 13 OctBaar 14:27−1 min—
Mon 12 OctBaar 14:28No data—
Sun 11 OctBaar 14:280 min—
Sat 10 OctBaar 14:29+1 min—