SN1 13814 Olten – Luzern

View line SN1

Olten 02:32 → Luzern 03:25 Sat, Sun 0 h 53 min · 14 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Luzern at 03:25 0 min

  1. Olten02:32
  2. Zofingen02:39
  3. Reiden02:44
  4. Sursee02:57
  5. Sempach-Neuenkirch03:08
  6. Emmenbrücke Gersag03:17
  7. Luzern03:25

Next service: tomorrow 02:32 from Olten · Sun 8 Nov

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

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

  • Early 0% · 0
  • On time 100% · 10
  • 3–10 min 0% · 0
  • 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=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 10 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:32on time on time
02:35≈ on time ≈ on time
02:39≈ on time ≈ on time
02:42≈ on time ≈ on time
02:44≈ on time ≈ on time
02:47≈ on time ≈ on time
02:50≈ on time ≈ on time
02:57 / 03:01≈ on time ≈ on time
03:04≈ on time ≈ on time
03:08≈ on time ≈ on time
03:14≈ on time ≈ on time
03:17≈ on time ≈ on time
03:19≈ on time ≈ on time
03:25on time on time

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 03:240 min—
Sun 1 NovLuzern 03:260 min—
Sat 31 OctLuzern 03:260 min—
Sun 25 OctLuzern 03:28+2 min+2 min
Sat 24 OctLuzern 03:260 min—
Sun 18 OctLuzern 03:260 min—
Sat 17 OctLuzern 03:260 min—
Sun 11 OctLuzern 03:260 min—
Sat 10 OctLuzern 03:260 min—
Sun 4 OctLuzern 03:260 min—