S29 8947 Sursee – Turgi

View line S29

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

✓ Today’s run finished

Today it reached Turgi at 12:58 +2 min

  1. Sursee11:51
  2. Nebikon12:01
  3. Reiden12:07
  4. Aarburg-Oftringen12:17
  5. Rupperswil12:38
  6. Holderbank AG12:44
  7. Turgi12:56

Next service: tomorrow 11:51 from Sursee · Wed 18 Nov

Next departure 11:51 tomorrow · Sursee
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
98%
39/40 runs under 3 min
RT coverage: 40 full · 0 partial · 11 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

  • Mon 5 Oct Max en route +10 min · last fix heading to Turgi +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 39
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 0% M n=1
  • 100% T n=8
  • 100% W n=7
  • 100% T n=3
  • 100% F n=6
  • 100% S n=8
  • 100% S n=7

Stops and timetable

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

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