S29 8940 Turgi – Sursee

View line S29

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

Running now · updated 11:33

Position estimated from the timetable

Between Aarau and Olten 0 min

Estimated arrival at Sursee 12:08 · 79 km/h

  1. Turgi11:02
  2. Holderbank AG11:15
  3. Rupperswil11:20
  4. Aarau11:25
  5. Olten11:36
  6. Aarburg-Oftringen11:40
  7. Sursee12:08

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

On-time · 30 days
78%
18/23 runs under 3 min
RT coverage: 22 full · 1 partial · 7 no data
On-time · 90 days
84%
38/45 runs under 3 min
RT coverage: 44 full · 1 partial · 9 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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 +13 min · last fix heading to Sursee +13 min
  • Sun 18 Oct Max en route +7 min · last fix heading to Sursee +7 min
  • Wed 28 Oct Max en route +4 min · last fix heading to Sursee +4 min
  • Mon 7 Sept Max en route +4 min · last fix heading to St. Erhard-Knutwil +4 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Sursee +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 38
  • 3–10 min 13% · 6
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=9
  • 86% W n=7
  • 50% T n=2
  • 100% F n=8
  • 83% S n=6
  • 67% S n=9

Stops and timetable

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

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