S27 20732 Baden – Bad Zurzach

View line S27

Baden 07:24 → Bad Zurzach 07:54 Daily 0 h 30 min · 9 stops SBB CFF FFS

✓ Today’s run finished

Today, last fix heading to Waldshut at 10:24 0 min

  1. Baden07:24
  2. Turgi07:29
  3. Döttingen07:37
  4. Klingnau07:39
  5. Koblenz07:43
  6. Rietheim07:51
  7. Bad Zurzach07:54

Next service: tomorrow 07:24 from Baden · Tue 10 Nov

Next departure 07:24 tomorrow · Baden
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 26 full · 3 partial · 1 no data
On-time · 90 days
97%
37/38 runs under 3 min
RT coverage: 35 full · 3 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 Bad Zurzach, 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 17 Oct Max en route +6 min · last fix heading to Waldshut +6 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=5
  • 83% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 38 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
07:24on time on time
07:29≈ on time ≈ on time
07:32≈ on time ≈ on time
07:37 / 07:38≈ on time ≈ +1 min
07:39≈ on time ≈ +1 min
07:43 / 07:46≈ on time ≈ +1 min
07:48≈ on time ≈ +1 min
07:51≈ on time ≈ +1 min
07:54on time +1 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 9 NovWaldshut 10:24Partial coverage0 min—
Sun 8 NovWaldshut 10:240 min—
Sat 7 NovWaldshut 10:240 min—
Fri 6 NovWaldshut 10:24Partial coverage0 min—
Thu 5 NovWaldshut 10:240 min—
Wed 4 NovWaldshut 10:240 min—
Tue 3 NovWaldshut 10:240 min—
Mon 2 NovWaldshut 10:240 min—
Sun 1 NovWaldshut 10:240 min—
Sat 31 OctWaldshut 10:240 min—
Fri 30 OctWaldshut 10:240 min—
Thu 29 OctWaldshut 10:24No data—
Wed 28 OctWaldshut 10:240 min—
Tue 27 OctWaldshut 10:240 min—
Mon 26 OctWaldshut 10:250 min—
Sun 25 OctWaldshut 10:240 min—
Sat 24 OctWaldshut 10:240 min—
Fri 23 OctWaldshut 10:240 min—
Thu 22 OctWaldshut 10:240 min—
Wed 21 OctWaldshut 10:240 min—
Tue 20 OctWaldshut 10:250 min—
Mon 19 OctWaldshut 10:240 min—
Sun 18 OctWaldshut 10:250 min—
Sat 17 OctWaldshut 10:30Partial coverage+6 min+6 min
Fri 16 OctKoblenz 10:14+1 min+1 min
Thu 15 OctKoblenz 10:15+1 min—
Wed 14 OctKoblenz 10:140 min—
Tue 13 OctKoblenz 10:150 min—
Mon 12 OctKoblenz 10:15+1 min+1 min
Sun 11 OctKoblenz 10:15+1 min—