S29 8919 Sursee – Turgi

View line S29

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

✓ Today’s run finished

Today it reached Turgi at 05:56 0 min

  1. Sursee04:51
  2. Nebikon05:01
  3. Reiden05:07
  4. Aarburg-Oftringen05:17
  5. Rupperswil05:38
  6. Holderbank AG05:44
  7. Turgi05:56

Next service: tomorrow 04:51 from Sursee · Sun 8 Nov

Next departure 04:51 tomorrow · Sursee
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
38/39 runs under 3 min
RT coverage: 39 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Thu 15 Oct Max en route +5 min · last fix heading to Turgi +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 38
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=6
  • 100% W n=5
  • 80% T n=5
  • 100% F n=6
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

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