SN1 13812 Sursee – Luzern

View line SN1

Sursee 02:01 → Luzern 02:25 Sat, Sun 0 h 24 min · 7 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Luzern at 02:25 0 min

  1. Sursee02:01
  2. Nottwil02:04
  3. Sempach-Neuenkirch02:08
  4. Emmenbrücke Kapf02:14
  5. Emmenbrücke Gersag02:17
  6. Emmenbrücke02:19
  7. Luzern02:25

Next service: tomorrow 02:01 from Sursee · Sun 8 Nov

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

  • Sun 1 Nov Max en route +5 min · last fix heading to Luzern +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 7
  • 3–10 min 13% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=4
  • 75% S n=4

Stops and timetable

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

Last 90 days, 8 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
02:01on time +2 min
02:04≈ on time ≈ +2 min
02:08≈ on time ≈ +2 min
02:14≈ on time ≈ +2 min
02:17≈ on time ≈ +2 min
02:19≈ on time ≈ +2 min
02:25on time +3 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 NovLuzern 02:270 min—
Sun 1 NovLuzern 02:30+4 min+5 min
Sat 31 OctLuzern 02:260 min—
Sun 25 OctLuzern 02:26No data—
Sat 24 OctLuzern 02:260 min—
Sun 18 OctLuzern 02:28+2 min+2 min
Sat 17 OctLuzern 02:26−1 min—
Sun 11 OctLuzern 02:28+2 min+2 min
Sat 10 OctLuzern 02:27No data—
Sun 4 OctLuzern 02:260 min—