S1 21190 Sursee – Luzern

View line S1

Sursee 01:10 → Luzern 01:37 Daily 0 h 27 min · 9 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Luzern at 01:38 +1 min

  1. Sursee01:10
  2. Oberkirch LU01:12
  3. Sempach-Neuenkirch01:19
  4. Rothenburg Station01:23
  5. Emmenbrücke Kapf01:26
  6. Emmenbrücke01:31
  7. Luzern01:37

Next service: tomorrow 01:10 from Sursee · Fri 6 Nov

Next departure 01:10 tomorrow · Sursee
On-time · 30 days
74%
20/27 runs under 3 min
RT coverage: 27 full · 0 partial · 3 no data
On-time · 90 days
76%
52/68 runs under 3 min
RT coverage: 68 full · 0 partial · 3 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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 30 Oct Max en route +9 min · last fix heading to Luzern +9 min
  • Sat 17 Oct Max en route +6 min · last fix heading to Luzern +6 min
  • Tue 18 Aug Max en route +6 min · last fix heading to Emmenbrücke +6 min
  • Sun 4 Oct Max en route +6 min · last fix heading to Luzern +6 min
  • Mon 17 Aug Max en route +5 min · last fix heading to Baar +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 76% · 52
  • 3–10 min 24% · 16
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 75% T n=8
  • 64% W n=11
  • 75% T n=12
  • 80% F n=10
  • 88% S n=8
  • 70% S n=10

Stops and timetable

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

Last 90 days, 68 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
01:10on time +1 min
01:12≈ on time ≈ +1 min
01:15≈ on time ≈ +1 min
01:19≈ +1 min ≈ +2 min
01:23≈ +1 min ≈ +2 min
01:26≈ +1 min ≈ +3 min
01:29≈ +1 min ≈ +3 min
01:31≈ +1 min ≈ +3 min
01:37+1 min +4 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
Thu 5 NovLuzern 01:39+1 min—
Wed 4 NovLuzern 01:42+4 min+4 min
Tue 3 NovLuzern 01:38No data—
Mon 2 NovLuzern 01:39+1 min+1 min
Sun 1 NovLuzern 01:41+3 min+3 min
Sat 31 OctLuzern 01:39+1 min—
Fri 30 OctLuzern 01:47+9 min+9 min
Thu 29 OctLuzern 01:41+3 min+3 min
Wed 28 OctLuzern 01:39+1 min—
Tue 27 OctLuzern 01:38No data—
Mon 26 OctLuzern 01:46+1 min—
Sun 25 OctLuzern 01:49+4 min+4 min
Sat 24 OctLuzern 01:47+2 min+2 min
Fri 23 OctLuzern 01:380 min—
Thu 22 OctLuzern 01:38+1 min—
Wed 21 OctLuzern 01:380 min—
Tue 20 OctLuzern 01:38+1 min—
Mon 19 OctLuzern 01:380 min—
Sun 18 OctLuzern 01:40+1 min+1 min
Sat 17 OctLuzern 01:44+6 min+6 min
Fri 16 OctLuzern 01:39+1 min+1 min
Thu 15 OctLuzern 01:380 min—
Wed 14 OctLuzern 01:42+4 min+4 min
Tue 13 OctLuzern 01:38No data—
Mon 12 OctLuzern 01:380 min—
Sun 11 OctLuzern 01:40+2 min+2 min
Sat 10 OctLuzern 01:40+1 min+1 min
Fri 9 OctLuzern 01:40+2 min+2 min
Thu 8 OctLuzern 01:42+4 min+4 min
Wed 7 OctLuzern 01:380 min—