S29 8953 Zofingen – Turgi

View line S29

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

✓ Today’s run finished

Today it reached Turgi at 14:22 0 min

  1. Zofingen13:39
  2. Olten13:48
  3. Aarau13:57
  4. Wildegg14:05
  5. Holderbank AG14:08
  6. Brugg AG14:16
  7. Turgi14:22

Next service: tomorrow 13:39 from Zofingen · Thu 19 Nov

Next departure 13:39 tomorrow · Zofingen
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
98%
42/43 runs under 3 min
RT coverage: 43 full · 0 partial · 11 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

  • Sat 17 Oct Max en route +3 min · last fix heading to Turgi +3 min

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 98% · 42
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=8
  • 100% W n=8
  • 100% T n=3
  • 100% F n=8
  • 86% S n=7
  • 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
13:39on time on time
13:44≈ on time ≈ on time
13:48 / 13:49≈ on time ≈ on time
13:57 / 13:58≈ on time ≈ +1 min
14:02≈ on time ≈ +1 min
14:05 / 14:06≈ on time ≈ +1 min
14:08≈ on time ≈ +1 min
14:11≈ on time ≈ +1 min
14:16 / 14:18≈ on time ≈ +1 min
14: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
Wed 18 NovTurgi 14:230 min—
Tue 17 NovTurgi 14:230 min—
Mon 16 NovTurgi 14:23No data—
Sun 15 NovTurgi 14:230 min—
Sat 14 NovTurgi 14:230 min—
Fri 13 NovTurgi 14:240 min—
Thu 12 NovTurgi 14:23No data—
Wed 11 NovTurgi 14:230 min—
Tue 10 NovTurgi 14:230 min—
Mon 9 NovTurgi 14:23No data—
Sun 8 NovTurgi 14:230 min—
Sat 7 NovTurgi 14:220 min—
Fri 6 NovTurgi 14:230 min—
Thu 5 NovTurgi 14:23No data—
Wed 4 NovTurgi 14:24+2 min+2 min
Tue 3 NovTurgi 14:24+1 min+1 min
Mon 2 NovTurgi 14:23No data—
Sun 1 NovTurgi 14:230 min—
Sat 31 OctTurgi 14:230 min—
Fri 30 OctTurgi 14:230 min—
Thu 29 OctTurgi 14:23No data—
Wed 28 OctTurgi 14:230 min—
Tue 27 OctTurgi 14:230 min—
Mon 26 OctTurgi 14:23No data—
Sun 25 OctTurgi 14:220 min—
Sat 24 OctTurgi 14:230 min—
Fri 23 OctTurgi 14:230 min—
Thu 22 OctTurgi 14:23No data—
Wed 21 OctTurgi 14:26+3 min+3 min
Tue 20 OctTurgi 14:230 min—