S29 8937 Zofingen – Turgi

View line S29

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

✓ Today’s run finished

Today, last fix heading to Turgi at 10:23 No data

  1. Zofingen09:39
  2. Olten09:48
  3. Aarau09:57
  4. Wildegg10:05
  5. Holderbank AG10:08
  6. Brugg AG10:16
  7. Turgi10:22

Next service: tomorrow 09:39 from Zofingen · Fri 20 Nov

Next departure 09:39 tomorrow · Zofingen
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
98%
44/45 runs under 3 min
RT coverage: 45 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Sun 18 Oct Max en route +4 min · last fix heading to Turgi +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 45 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
09:39on time on time
09:44≈ on time ≈ on time
09:48 / 09:49≈ on time ≈ on time
09:57 / 09:58≈ on time ≈ on time
10:02≈ on time ≈ on time
10:05 / 10:06≈ on time ≈ on time
10:08≈ on time ≈ on time
10:11≈ on time ≈ on time
10:16 / 10:18≈ on time ≈ on time
10:22on time on time

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