S29 8973 Zofingen → Turgi

View line S29

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

S29 8973 Zofingen–Turgi: final delay under 3 min on 29 of its 29 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 06:46 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 18:39 from Zofingen · Sun 22 Nov

Next departure 18:39 today · Zofingen
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
94%
51/54 runs under 3 min
RT coverage: 54 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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 22 Oct Max en route +5 min · last fix heading to Turgi +5 min
  • Fri 23 Oct Max en route +4 min · last fix heading to Turgi +4 min
  • Thu 15 Oct Max en route +4 min · last fix heading to Turgi +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 51
  • 3–10 min 6% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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