S1 21107 Luzern – Sursee

View line S1

Luzern 04:21 → Sursee 04:50 Daily 0 h 29 min · 9 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Sursee at 04:50 0 min

  1. Luzern04:21
  2. Emmenbrücke04:26
  3. Emmenbrücke Kapf04:31
  4. Rothenburg Station04:34
  5. Sempach-Neuenkirch04:39
  6. Oberkirch LU04:46
  7. Sursee04:50

Next service: tomorrow 04:21 from Luzern · Sun 8 Nov

Next departure 04:21 tomorrow · Luzern
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
93%
68/73 runs under 3 min
RT coverage: 73 full · 0 partial · 9 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: +1 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

  • Tue 15 Sept Max en route +5 min · last fix heading to Cham +5 min
  • Sun 16 Aug Max en route +5 min · last fix heading to Hünenberg Zythus +5 min
  • Wed 16 Sept Max en route +5 min · last fix heading to Hünenberg Zythus +5 min
  • Fri 18 Sept Max en route +4 min · last fix heading to Rotkreuz +4 min
  • Tue 22 Sept Max en route +3 min · last fix heading to Rotkreuz +3 min

Distribution · 90 days

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

  • Early 5% · 4
  • On time 88% · 64
  • 3–10 min 7% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 80% T n=10
  • 91% W n=11
  • 100% T n=11
  • 91% F n=11
  • 100% S n=13
  • 80% S n=5

Stops and timetable

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

Last 90 days, 73 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
04:21on time +1 min
04:26≈ on time ≈ +1 min
04:28≈ on time ≈ +1 min
04:31≈ on time ≈ +1 min
04:34≈ on time ≈ +1 min
04:39≈ on time ≈ +1 min
04:43≈ on time ≈ +2 min
04:46≈ on time ≈ +2 min
04:50on 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
Sat 7 NovSursee 04:490 min—
Fri 6 NovSursee 04:490 min—
Thu 5 NovSursee 04:490 min—
Wed 4 NovSursee 04:490 min—
Tue 3 NovSursee 04:490 min—
Mon 2 NovSursee 04:49−1 min—
Sun 1 NovSursee 04:510 min—
Sat 31 OctSursee 04:510 min—
Fri 30 OctSursee 04:510 min—
Thu 29 OctSursee 04:50−1 min—
Wed 28 OctSursee 04:510 min—
Tue 27 OctSursee 04:52+1 min—
Mon 26 OctSursee 04:510 min—
Sun 25 OctSursee 04:51+1 min—
Sat 24 OctSursee 04:510 min—
Fri 23 OctSursee 04:510 min—
Thu 22 OctSursee 04:510 min—
Wed 21 OctSursee 04:510 min—
Tue 20 OctSursee 04:510 min—
Mon 19 OctSursee 04:50−1 min—
Sun 18 OctSursee 04:52No data—
Sat 17 OctSursee 04:510 min—
Fri 16 OctSursee 04:51No data—
Thu 15 OctSursee 04:51No data—
Wed 14 OctSursee 04:51No data—
Tue 13 OctSursee 04:51No data—
Mon 12 OctSursee 04:51No data—
Sun 11 OctSursee 04:51No data—
Sat 10 OctSursee 04:53+1 min+1 min
Fri 9 OctSursee 04:50−1 min—