S6 18679 Baden – Uetikon

View line S6

Baden 20:21 → Uetikon 21:27 Daily 1 h 06 min · 22 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Uetikon at 21:31 +4 min

  1. Baden20:21
  2. Otelfingen Golfpark20:34
  3. Zürich Affoltern20:44
  4. Zürich HB20:58
  5. Zollikon21:08
  6. Winkel am Zürichsee21:17
  7. Uetikon21:27

Next service: tomorrow 20:21 from Baden · Tue 10 Nov

Next departure 20:21 tomorrow · Baden
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
94%
51/54 runs under 3 min
RT coverage: 54 full · 0 partial · 0 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 Uetikon, 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 25 Sept Max en route +9 min · last fix heading to Herrliberg-Feldmeilen +9 min
  • Mon 9 Nov Max en route +4 min · last fix heading to Uetikon +4 min
  • Tue 22 Sept Max en route +3 min · last fix heading to Uetikon +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (22 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 10
20:21on time on time
20:24≈ on time ≈ on time
20:28≈ on time ≈ on time
20:32 / 20:33≈ on time ≈ on time
20:34≈ on time ≈ on time
20:37≈ on time ≈ +1 min
20:40 / 20:41≈ on time ≈ +1 min
20:44≈ on time ≈ +1 min
20:47≈ on time ≈ +1 min
20:50 / 20:51≈ on time ≈ +1 min
20:55≈ on time ≈ +1 min
20:58 / 21:00≈ on time ≈ +1 min
21:02 / 21:03≈ on time ≈ +1 min
21:06≈ on time ≈ +1 min
21:08≈ on time ≈ +1 min
21:10≈ on time ≈ +1 min
21:12 / 21:13≈ on time ≈ +1 min
21:15≈ on time ≈ +1 min
21:17≈ on time ≈ +1 min
21:20≈ on time ≈ +1 min
21:23≈ on time ≈ +1 min
21:27on 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 NovUetikon 21:32+4 min+4 min
Sun 8 NovMeilen 21:240 min—
Sat 7 NovMeilen 21:24+1 min—
Fri 6 NovUetikon 21:28+1 min—
Thu 5 NovUetikon 21:28+1 min—
Wed 4 NovUetikon 21:280 min—
Tue 3 NovUetikon 21:280 min—
Mon 2 NovUetikon 21:280 min—
Sun 1 NovUetikon 21:28−1 min—
Sat 31 OctUetikon 21:280 min—
Fri 30 OctUetikon 21:280 min—
Thu 29 OctUetikon 21:280 min—
Wed 28 OctUetikon 21:28−1 min—
Tue 27 OctUetikon 21:280 min—
Mon 26 OctUetikon 21:280 min—
Sun 25 OctUetikon 21:27−1 min—
Sat 24 OctUetikon 21:280 min—
Fri 23 OctUetikon 21:29+1 min+1 min
Thu 22 OctUetikon 21:280 min—
Wed 21 OctUetikon 21:280 min—
Tue 20 OctUetikon 21:280 min—
Mon 19 OctUetikon 21:280 min+2 min
Sun 18 OctUetikon 21:280 min—
Sat 17 OctUetikon 21:270 min—
Fri 16 OctUetikon 21:280 min—
Thu 15 OctUetikon 21:280 min—
Wed 14 OctUetikon 21:290 min—
Tue 13 OctUetikon 21:27−1 min—
Mon 12 OctUetikon 21:280 min—
Sun 11 OctUetikon 21:29+1 min+1 min