S17 7605 Bremgarten → Dietikon

View line S17

Bremgarten 05:34 → Dietikon 05:57 Daily 0 h 23 min · 14 stops Aargau Verkehr

S17 7605 Bremgarten–Dietikon: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, 1 min late. Expected at Dietikon: 05:58. TrainsRadar data as of 22 Nov 2026, 05:55 (GMT+1).

Running now · updated 05:54

Position estimated from the timetable

Between Dietikon Schöneggstrasse and Dietikon +1 min

Estimated arrival at Dietikon 05:58 05:57 · 10 km/h

  1. Bremgarten05:34
  2. Zufikon05:36
  3. Widen Heinrüti05:40
  4. Rudolfstetten Hofacker05:46
  5. Reppischhof05:49
  6. Dietikon Schöneggstrasse05:53
  7. Dietikon05:57

Today it is running worse than usual: typical arrival delay is 0 min; 100% of the last 30 runs arrived on time.

On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
54/54 runs under 3 min
RT coverage: 54 full · 0 partial · 1 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 Dietikon, 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

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

  • Early 13% · 7
  • On time 87% · 47
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (14 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 10Today
05:34on time on timePassed
05:35≈ on time ≈ on timePassed
05:36≈ on time ≈ on timePassed
05:38≈ on time ≈ on timePassed
05:40≈ on time ≈ on timePassed
05:41≈ on time ≈ on timePassed
05:43 / 05:44≈ on time ≈ on timePassed
05:46≈ on time ≈ on timePassed
05:47≈ on time ≈ +1 minPassed
05:49≈ on time ≈ +1 minPassed
05:51≈ on time ≈ +1 minPassed
05:52≈ on time ≈ +1 minPassed
05:53≈ on time ≈ +1 minPassed
05:57on time +1 minNext

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
Sun 22 NovDietikon 05:54+1 min+1 min
Sat 21 NovDietikon 05:580 min—
Fri 20 NovBolligen 06:49+1 min+1 min
Thu 19 NovBolligen 06:490 min+1 min
Wed 18 NovBolligen 06:49+1 min+1 min
Tue 17 NovBolligen 06:49+1 min+1 min
Mon 16 NovBolligen 06:49+1 min+1 min
Sun 15 NovDietikon 05:59+1 min—
Sat 14 NovDietikon 05:590 min—
Fri 13 NovBolligen 06:490 min+1 min
Thu 12 NovBolligen 06:50+1 min+1 min
Wed 11 NovBolligen 06:490 min—
Tue 10 NovBolligen 06:49−1 min—
Mon 9 NovBolligen 06:49+1 min—
Sun 8 NovDietikon 05:580 min+1 min
Sat 7 NovDietikon 05:540 min—
Fri 6 NovBolligen 06:49+1 min+1 min
Thu 5 NovBolligen 06:49+2 min+2 min
Wed 4 NovBolligen 06:480 min—
Tue 3 NovBolligen 06:49+1 min+1 min
Mon 2 NovBolligen 06:490 min+1 min
Sun 1 NovDietikon 05:57−1 min—
Sat 31 OctDietikon 05:57−1 min—
Fri 30 OctBolligen 06:50+1 min—
Thu 29 OctBolligen 06:50+1 min—
Wed 28 OctBolligen 06:51+1 min+1 min
Tue 27 OctBolligen 06:490 min—
Mon 26 OctBolligen 06:48−1 min+1 min
Sun 25 OctDietikon 05:56−1 min—
Sat 24 OctDietikon 05:56−1 min—