S29 8941 Zofingen – Turgi

View line S29

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

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 10:39 from Zofingen · Tue 17 Nov

Next departure 10:39 today · Zofingen
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
100%
43/43 runs under 3 min
RT coverage: 43 full · 0 partial · 1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 43
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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