S29 8928 Turgi – Sursee

View line S29

Turgi 08:02 → Sursee 09:08 Daily 1 h 06 min · 17 stops SBB CFF FFS

Running now · updated 08:36

Position estimated from the timetable

Between Olten and Aarburg-Oftringen 0 min

Estimated arrival at Sursee 09:08 · 64 km/h

  1. Turgi08:02
  2. Holderbank AG08:15
  3. Rupperswil08:20
  4. Olten08:36
  5. Aarburg-Oftringen08:40
  6. Reiden08:50
  7. Sursee09:08

Today it is running no worse than usual: typical arrival delay is +1 min; 90% of the last 30 runs arrived on time.

On-time · 30 days
90%
27/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
92%
47/51 runs under 3 min
RT coverage: 50 full · 1 partial · 2 no data
Typical delay
+1min
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 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

  • Fri 30 Oct Max en route +5 min · last fix heading to Sursee +5 min
  • Sun 11 Oct Max en route +4 min · last fix heading to Sursee +4 min
  • Wed 28 Oct Max en route +4 min · last fix heading to Sursee +4 min
  • Tue 10 Nov Max en route +3 min · last fix heading to Sursee +3 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 90% · 46
  • 3–10 min 8% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 83% T n=6
  • 86% W n=7
  • 100% T n=6
  • 89% F n=9
  • 100% S n=7
  • 88% S n=8

Stops and timetable

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

Last 90 days, 51 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 10Today
08:02on time on timePassed
08:07≈ on time ≈ on timePassed
08:12≈ on time ≈ on timePassed
08:15≈ on time ≈ +1 minPassed
08:17≈ on time ≈ +1 minPassed
08:20≈ on time ≈ +1 minPassed
08:25 / 08:26≈ on time ≈ +1 minPassed
08:36≈ on time ≈ +1 minPassed
08:40≈ on time ≈ +2 minNext
08:44≈ on time ≈ +2 min
08:47≈ on time ≈ +2 min
08:50≈ on time ≈ +2 min
08:53≈ on time ≈ +2 min
08:57≈ on time ≈ +2 min
09:00≈ on time ≈ +2 min
09:04≈ on time ≈ +3 min
09:08+1 min +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
Mon 16 NovOlten 08:34Partial coverage0 min—
Sun 15 NovSursee 09:09+1 min—
Sat 14 NovSursee 09:090 min—
Fri 13 NovSursee 09:090 min—
Thu 12 NovSursee 09:090 min—
Wed 11 NovSursee 09:09+1 min—
Tue 10 NovSursee 09:12+3 min+3 min
Mon 9 NovSursee 09:09+1 min—
Sun 8 NovSursee 09:09+1 min+1 min
Sat 7 NovSursee 09:09+1 min—
Fri 6 NovSursee 09:090 min—
Thu 5 NovSursee 09:090 min—
Wed 4 NovSursee 09:090 min—
Tue 3 NovSursee 09:090 min—
Mon 2 NovSursee 09:08−1 min—
Sun 1 NovSursee 09:09+1 min—
Sat 31 OctSursee 09:10+2 min+2 min
Fri 30 OctSursee 09:14+5 min+5 min
Thu 29 OctSursee 09:090 min—
Wed 28 OctSursee 09:13+4 min+4 min
Tue 27 OctSursee 09:11+2 min+2 min
Mon 26 OctTurgi 11:01+1 min—
Sun 25 OctSursee 09:12+3 min+3 min
Sat 24 OctSursee 09:11+2 min+2 min
Fri 23 OctSursee 09:090 min—
Thu 22 OctSursee 09:090 min—
Wed 21 OctSursee 09:10+1 min—
Tue 20 OctSursee 09:100 min—
Mon 19 OctSursee 09:11+3 min+3 min
Sun 18 OctSursee 09:10+1 min+1 min