S29 8946 Turgi – Zofingen

View line S29

Turgi 12:34 → Zofingen 13:21 Daily 0 h 47 min · 10 stops SBB CFF FFS

It has not run yet today

Last recorded run: Monday 16 November No data

Next service: today 12:34 from Turgi · Tue 17 Nov

Next departure 12:34 today · Turgi
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
100%
39/39 runs under 3 min
RT coverage: 39 full · 0 partial · 11 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 Zofingen, 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

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

  • Early 3% · 1
  • On time 97% · 38
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=8
  • 100% W n=8
  • 100% T n=3
  • 100% F n=7
  • 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, 39 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
12:34on time on time
12:40 / 12:43≈ on time ≈ on time
12:47≈ on time ≈ on time
12:49≈ on time ≈ +1 min
12:52≈ on time ≈ +1 min
12:55≈ on time ≈ +1 min
13:00 / 13:01≈ on time ≈ +1 min
13:11 / 13:12≈ on time ≈ +2 min
13:15 / 13:16≈ on time ≈ +2 min
13:21on 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
Mon 16 NovZofingen 13:22No data—
Sun 15 NovZofingen 13:23+1 min—
Sat 14 NovZofingen 13:220 min—
Fri 13 NovZofingen 13:23+1 min—
Thu 12 NovZofingen 13:22No data—
Wed 11 NovZofingen 13:220 min—
Tue 10 NovZofingen 13:23+1 min—
Mon 9 NovZofingen 13:22No data—
Sun 8 NovZofingen 13:220 min—
Sat 7 NovZofingen 13:220 min—
Fri 6 NovZofingen 13:23+1 min—
Thu 5 NovZofingen 13:22No data—
Wed 4 NovZofingen 13:23+1 min—
Tue 3 NovZofingen 13:230 min—
Mon 2 NovZofingen 13:22No data—
Sun 1 NovZofingen 13:220 min—
Sat 31 OctZofingen 13:220 min—
Fri 30 OctZofingen 13:220 min—
Thu 29 OctZofingen 13:22No data—
Wed 28 OctZofingen 13:230 min—
Tue 27 OctZofingen 13:23+1 min—
Mon 26 OctZofingen 13:22No data—
Sun 25 OctZofingen 13:24+2 min+2 min
Sat 24 OctZofingen 13:220 min—
Fri 23 OctZofingen 13:23+1 min+1 min
Thu 22 OctZofingen 13:22No data—
Wed 21 OctZofingen 13:25+3 min+3 min
Tue 20 OctZofingen 13:220 min—
Mon 19 OctZofingen 13:22No data—
Sun 18 OctZofingen 13:23+1 min+1 min