SN1 13816 Olten – Sursee

View line SN1

Olten 03:32 → Sursee 03:57 Sat, Sun 0 h 25 min · 8 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Sursee at 03:59 +2 min

  1. Olten03:32
  2. Aarburg-Oftringen03:35
  3. Zofingen03:39
  4. Reiden03:44
  5. Dagmersellen03:47
  6. Nebikon03:50
  7. Sursee03:57

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

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

  • Sun 25 Oct Max en route +6 min · last fix heading to Sursee +6 min
  • Sat 17 Oct Max en route +3 min · last fix heading to Sursee +3 min
  • Sat 24 Oct Max en route +3 min · last fix heading to Sursee +3 min

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 70% · 7
  • 3–10 min 30% · 3
  • 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
  • 60% S n=5
  • 80% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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
03:32+1 min +1 min
03:35≈ +1 min ≈ +1 min
03:39≈ +1 min ≈ +1 min
03:42≈ +1 min ≈ +2 min
03:44≈ +1 min ≈ +2 min
03:47≈ +1 min ≈ +2 min
03:50≈ +1 min ≈ +3 min
03:57+2 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
Sat 7 NovSursee 03:59+2 min+2 min
Sun 1 NovSursee 03:59+1 min+1 min
Sat 31 OctSursee 03:59+1 min—
Sun 25 OctSursee 04:04+6 min+6 min
Sat 24 OctSursee 04:01+3 min+3 min
Sun 18 OctSursee 04:00+2 min+2 min
Sat 17 OctSursee 04:02+3 min+3 min
Sun 11 OctSursee 04:00+2 min+2 min
Sat 10 OctSursee 04:00+1 min+1 min
Sun 4 OctSursee 03:59+1 min+1 min