S29 8932 Turgi – Sursee

View line S29

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

✓ Today’s run finished

Today it reached Sursee at 10:12 +4 min

  1. Turgi09:02
  2. Holderbank AG09:15
  3. Rupperswil09:20
  4. Aarburg-Oftringen09:40
  5. Reiden09:50
  6. Nebikon09:57
  7. Sursee10:08

Next service: tomorrow 09:02 from Turgi · Thu 19 Nov

Next departure 09:02 tomorrow · Turgi
On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
54/56 runs under 3 min
RT coverage: 56 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Mon 9 Nov Max en route +4 min · last fix heading to Sursee +4 min
  • Wed 18 Nov Max en route +4 min · last fix heading to Sursee +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 54
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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