S29 8999 Sursee – Olten

View line S29

Sursee 01:31 → Olten 02:00 Daily 0 h 29 min · 10 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Olten at 02:00 −1 min

  1. Sursee01:31
  2. Wauwil01:37
  3. Nebikon01:40
  4. Reiden01:46
  5. Brittnau-Wikon01:48
  6. Aarburg-Oftringen01:55
  7. Olten02:00

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

Next departure 01:31 tomorrow · Sursee
On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
92%
55/60 runs under 3 min
RT coverage: 60 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Olten, 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 23 Oct Max en route +8 min · last fix heading to Olten +8 min
  • Tue 13 Oct Max en route +7 min · last fix heading to Olten +7 min
  • Sat 5 Sept Max en route +6 min · last fix heading to Aarburg-Oftringen +6 min
  • Mon 7 Sept Max en route +7 min · last fix heading to Olten +6 min
  • Sat 29 Aug Max en route +14 min · last fix heading to Olten +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 55
  • 3–10 min 8% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 90% T n=10
  • 100% W n=8
  • 100% T n=8
  • 88% F n=8
  • 78% S n=9
  • 100% S n=8

Stops and timetable

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

Last 90 days, 60 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:31on time +1 min
01:33≈ on time ≈ +1 min
01:37≈ on time ≈ +1 min
01:40≈ on time ≈ +2 min
01:43≈ on time ≈ +2 min
01:46≈ on time ≈ +2 min
01:48≈ on time ≈ +2 min
01:52≈ on time ≈ +2 min
01:55 / 01:56≈ on time ≈ +2 min
02:00on 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
Thu 5 NovOlten 01:24−1 min—
Wed 4 NovOlten 01:24+1 min—
Tue 3 NovOlten 01:28+3 min+3 min
Mon 2 NovOlten 01:240 min—
Sun 1 NovOlten 01:27+2 min+2 min
Sat 31 OctOlten 01:250 min—
Fri 30 OctOlten 01:26+1 min+1 min
Thu 29 OctOlten 01:250 min—
Wed 28 OctOlten 01:26+1 min—
Tue 27 OctOlten 01:250 min—
Mon 26 OctOlten 01:250 min—
Sun 25 OctOlten 01:27+3 min+3 min
Sat 24 OctOlten 01:27+2 min+2 min
Fri 23 OctOlten 01:36+8 min+8 min
Thu 22 OctOlten 01:30+2 min+2 min
Wed 21 OctOlten 01:29+1 min+1 min
Tue 20 OctOlten 01:31+3 min+3 min
Mon 19 OctOlten 01:32+1 min—
Sun 18 OctOlten 01:27+1 min+1 min
Sat 17 OctOlten 01:27+2 min+2 min
Fri 16 OctOlten 01:250 min—
Thu 15 OctOlten 01:25−1 min—
Wed 14 OctOlten 01:250 min—
Tue 13 OctOlten 01:25+7 min+7 min
Mon 12 OctOlten 01:31+1 min—
Sun 11 OctOlten 01:26+1 min—
Sat 10 OctOlten 01:28+3 min+3 min
Fri 9 OctOlten 01:250 min—
Thu 8 OctOlten 01:250 min—
Wed 7 OctOlten 01:250 min—