S29 8965 Zofingen – Turgi

View line S29

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

It has not run yet today

Last recorded run: Thursday 19 November +2 min

Next service: today 16:39 from Zofingen · Fri 20 Nov

Next departure 16:39 today · Zofingen
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
92%
44/48 runs under 3 min
RT coverage: 48 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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 12 Nov Max en route +15 min · last fix heading to Turgi +15 min
  • Thu 15 Oct Max en route +4 min · last fix heading to Turgi +4 min
  • Wed 14 Oct Max en route +4 min · last fix heading to Turgi +4 min
  • Thu 22 Oct Max en route +3 min · last fix heading to Turgi +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 44
  • 3–10 min 6% · 3
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=8
  • 86% W n=7
  • 63% T n=8
  • 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 (10 stops).

Last 90 days, 48 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
16:39on time on time
16:44≈ on time ≈ on time
16:48 / 16:49≈ on time ≈ +1 min
16:57 / 16:58≈ on time ≈ +1 min
17:02≈ on time ≈ +1 min
17:05 / 17:06≈ on time ≈ +2 min
17:08≈ on time ≈ +2 min
17:11≈ on time ≈ +2 min
17:16 / 17:18≈ on time ≈ +2 min
17:22on time +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
Thu 19 NovTurgi 17:24+2 min+2 min
Wed 18 NovTurgi 17:24+1 min+1 min
Tue 17 NovTurgi 17:24+1 min—
Mon 16 NovTurgi 17:24+2 min+2 min
Sun 15 NovTurgi 17:22−1 min—
Sat 14 NovTurgi 17:24+2 min+2 min
Fri 13 NovTurgi 17:230 min—
Thu 12 NovTurgi 17:37+15 min+15 min
Wed 11 NovTurgi 17:22−1 min—
Tue 10 NovTurgi 17:220 min—
Mon 9 NovTurgi 17:24+2 min+2 min
Sun 8 NovTurgi 17:230 min—
Sat 7 NovTurgi 17:220 min—
Fri 6 NovTurgi 17:24+1 min—
Thu 5 NovTurgi 17:230 min—
Wed 4 NovTurgi 17:230 min—
Tue 3 NovTurgi 17:230 min—
Mon 2 NovTurgi 17:230 min+1 min
Sun 1 NovTurgi 17:230 min—
Sat 31 OctTurgi 17:230 min—
Fri 30 OctTurgi 17:230 min—
Thu 29 OctTurgi 17:230 min—
Wed 28 OctTurgi 17:230 min—
Tue 27 OctTurgi 17:230 min—
Mon 26 OctTurgi 17:230 min—
Sun 25 OctTurgi 17:230 min—
Sat 24 OctTurgi 17:220 min—
Fri 23 OctTurgi 17:230 min—
Thu 22 OctTurgi 17:26+3 min+3 min
Wed 21 OctTurgi 17:24+2 min+2 min