S27 8737 Bad Zurzach → Baden

View line S27

Bad Zurzach 09:03 → Baden 09:33 Daily 0 h 30 min · 9 stops SBB CFF FFS

Running now · updated 09:30

Position estimated from the timetable

Between Turgi and Baden 0 min

Estimated arrival at Baden 09:33 · 52 km/h

  1. Bad Zurzach09:03
  2. Rietheim09:05
  3. Koblenz09:11
  4. Klingnau09:16
  5. Döttingen09:18
  6. Turgi09:28
  7. Baden09:33

Today it is running no worse than usual: typical arrival delay is +1 min; 96% of the last 28 runs arrived on time.

On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
98%
48/49 runs under 3 min
RT coverage: 49 full · 0 partial · 2 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Baden, 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 24 Oct Max en route +3 min · last fix heading to Baden +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 48
  • 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=7
  • 100% T n=5
  • 100% F n=8
  • 88% S n=8
  • 100% S n=7

Stops and timetable

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

Last 90 days, 49 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
09:03on time on timePassed
09:05≈ on time ≈ on timePassed
09:09≈ on time ≈ +1 minPassed
09:11 / 09:14≈ on time ≈ +1 minPassed
09:16≈ on time ≈ +1 minPassed
09:18 / 09:19≈ on time ≈ +1 minPassed
09:23≈ +1 min ≈ +1 minPassed
09:28≈ +1 min ≈ +2 minPassed
09:33+1 min +2 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
Sat 21 NovBaden 09:290 min—
Fri 20 NovBaden 09:340 min—
Thu 19 NovBaden 09:34No data—
Wed 18 NovBaden 09:340 min—
Tue 17 NovBaden 09:34+2 min+2 min
Mon 16 NovBaden 09:340 min—
Sun 15 NovBaden 09:340 min—
Sat 14 NovBaden 09:340 min—
Fri 13 NovBaden 09:34+1 min—
Thu 12 NovBaden 09:340 min—
Wed 11 NovBaden 09:34+1 min—
Tue 10 NovBaden 09:34+2 min+2 min
Mon 9 NovBaden 09:34+1 min+1 min
Sun 8 NovBaden 09:340 min—
Sat 7 NovBaden 09:340 min—
Fri 6 NovBaden 09:340 min—
Thu 5 NovBaden 09:340 min—
Wed 4 NovBaden 09:34+2 min+2 min
Tue 3 NovBaden 09:34+2 min+2 min
Mon 2 NovBaden 09:34+1 min+2 min
Sun 1 NovBaden 09:340 min—
Sat 31 OctBaden 09:35+1 min—
Fri 30 OctBaden 09:35+1 min—
Thu 29 OctBaden 09:34No data—
Wed 28 OctBaden 09:35+1 min+2 min
Tue 27 OctBaden 09:36+1 min+1 min
Mon 26 OctBad Zurzach 11:010 min—
Sun 25 OctBaden 09:35+1 min+1 min
Sat 24 OctBaden 09:37+3 min+3 min
Fri 23 OctBaden 09:35+1 min+1 min