S29 8989 Zofingen → Turgi

View line S29

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

S29 8989 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, 00:53 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

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

Next departure 22: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
98%
50/51 runs under 3 min
RT coverage: 51 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: +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

  • Fri 23 Oct Max en route +7 min · last fix heading to Turgi +7 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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