S29 8969 Zofingen – Turgi

View line S29

Zofingen 17:39 → Turgi 18:22 Daily 0 h 43 min · 10 stops SBB CFF FFS

Running now · updated 18:23

Position estimated from the timetable

Between Brugg AG and Turgi 0 min

Estimated arrival at Turgi 18:22 · 6 km/h

  1. Zofingen17:39
  2. Olten17:48
  3. Aarau17:57
  4. Wildegg18:05
  5. Holderbank AG18:08
  6. Brugg AG18:16
  7. Turgi18:22

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

On-time · 30 days
90%
27/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
93%
39/42 runs under 3 min
RT coverage: 42 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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 12 Nov Max en route +10 min · last fix heading to Turgi +10 min
  • Tue 10 Nov Max en route +5 min · last fix heading to Turgi +5 min
  • Fri 6 Nov Max en route +4 min · last fix heading to Turgi +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 39
  • 3–10 min 7% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 42 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
17:39on time on timePassed
17:44≈ on time ≈ on timePassed
17:48 / 17:49≈ on time ≈ on timePassed
17:57 / 17:58≈ on time ≈ +1 minPassed
18:02≈ on time ≈ +1 minPassed
18:05 / 18:06≈ on time ≈ +1 minPassed
18:08≈ on time ≈ +1 minPassed
18:11≈ on time ≈ +1 minPassed
18:16 / 18:18≈ on time ≈ +1 minPassed
18:22on time +1 minNext

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
Mon 16 NovTurgi 18:230 min—
Sun 15 NovTurgi 18:230 min—
Sat 14 NovTurgi 18:24+1 min+2 min
Fri 13 NovTurgi 18:230 min—
Thu 12 NovTurgi 18:32+10 min+10 min
Wed 11 NovTurgi 18:230 min—
Tue 10 NovTurgi 18:28+5 min+5 min
Mon 9 NovTurgi 18:24+1 min+1 min
Sun 8 NovTurgi 18:230 min—
Sat 7 NovTurgi 18:220 min—
Fri 6 NovTurgi 18:27+4 min+4 min
Thu 5 NovTurgi 18:230 min—
Wed 4 NovTurgi 18:230 min—
Tue 3 NovTurgi 18:230 min—
Mon 2 NovTurgi 18:230 min—
Sun 1 NovTurgi 18:230 min—
Sat 31 OctTurgi 18:230 min—
Fri 30 OctTurgi 18:230 min—
Thu 29 OctTurgi 18:230 min—
Wed 28 OctTurgi 18:23−1 min—
Tue 27 OctTurgi 18:230 min—
Mon 26 OctTurgi 18:230 min—
Sun 25 OctTurgi 18:230 min—
Sat 24 OctTurgi 18:24+1 min—
Fri 23 OctTurgi 18:230 min—
Thu 22 OctTurgi 18:230 min—
Wed 21 OctTurgi 18:23+1 min—
Tue 20 OctTurgi 18:230 min—
Mon 19 OctTurgi 18:230 min—
Sun 18 OctTurgi 18:200 min—