S29 8991 Sursee – Turgi

View line S29

Sursee 22:51 → Turgi 23:56 Daily 1 h 05 min · 17 stops SBB CFF FFS

Running now · updated 23:15

Position estimated from the timetable

Between Zofingen and Aarburg-Oftringen +1 min

Estimated arrival at Turgi 23:57 · 67 km/h

  1. Sursee22:51
  2. Nebikon23:01
  3. Reiden23:07
  4. Zofingen23:12
  5. Aarburg-Oftringen23:17
  6. Rupperswil23:38
  7. Turgi23:56

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

On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
92%
49/53 runs under 3 min
RT coverage: 52 full · 1 partial · 0 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 Turgi, 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 +7 min · last fix heading to Turgi +7 min
  • Sat 24 Oct Max en route +4 min · last fix heading to Turgi +4 min
  • Fri 2 Oct Max en route +3 min · last fix heading to Brugg AG +3 min
  • Sat 3 Oct Max en route +3 min · last fix heading to Turgi +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 100% W n=7
  • 100% T n=7
  • 71% F n=7
  • 75% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 53 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
22:51+1 min +1 minPassed
22:53≈ +1 min ≈ +1 minPassed
22:57≈ +1 min ≈ +1 minPassed
23:01≈ +1 min ≈ +1 minPassed
23:04≈ +1 min ≈ +1 minPassed
23:07≈ +1 min ≈ +1 minPassed
23:09≈ +1 min ≈ +1 minPassed
23:12 / 23:13≈ +1 min ≈ +1 minPassed
23:17≈ +1 min ≈ +1 minNext
23:22 / 23:23≈ +1 min ≈ +2 min
23:32 / 23:34≈ +1 min ≈ +2 min
23:38≈ +1 min ≈ +2 min
23:41 / 23:42≈ +1 min ≈ +2 min
23:44≈ +1 min ≈ +2 min
23:47≈ +1 min ≈ +2 min
23:52≈ +1 min ≈ +2 min
23:56+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
Tue 17 NovAarburg-Oftringen 23:14Partial coverage+1 min—
Mon 16 NovTurgi 23:570 min—
Sun 15 NovTurgi 23:58+1 min+1 min
Sat 14 NovTurgi 23:58+1 min—
Fri 13 NovTurgi 23:59+1 min+1 min
Thu 12 NovTurgi 23:58+1 min—
Wed 11 NovTurgi 23:570 min—
Tue 10 NovTurgi 23:58+1 min—
Mon 9 NovTurgi 23:59+1 min+1 min
Sun 8 NovTurgi 23:59+2 min+2 min
Sat 7 NovTurgi 23:58+2 min+2 min
Fri 6 NovTurgi 23:570 min—
Thu 5 NovOlten 23:24+1 min—
Wed 4 NovOlten 23:230 min—
Tue 3 NovOlten 23:230 min—
Mon 2 NovOlten 23:230 min—
Sun 1 NovTurgi 23:580 min—
Sat 31 OctTurgi 23:58+1 min—
Fri 30 OctTurgi 23:570 min—
Thu 29 OctTurgi 00:00+3 min+3 min
Wed 28 OctTurgi 00:00+3 min+3 min
Tue 27 OctTurgi 23:58+1 min—
Mon 26 OctTurgi 23:58+1 min—
Sun 25 OctTurgi 23:57+1 min+2 min
Sat 24 OctTurgi 00:00+4 min+4 min
Fri 23 OctTurgi 00:01+7 min+7 min
Thu 22 OctTurgi 23:58+1 min—
Wed 21 OctTurgi 23:57+1 min—
Tue 20 OctTurgi 23:57−1 min—
Mon 19 OctTurgi 23:560 min—