S6 18635 Baden – Uetikon

View line S6

Baden 18:51 → Uetikon 19:57 Daily 1 h 06 min · 22 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Uetikon at 19:57 0 min

  1. Baden18:51
  2. Otelfingen Golfpark19:04
  3. Zürich Affoltern19:14
  4. Zürich HB19:28
  5. Zollikon19:38
  6. Winkel am Zürichsee19:47
  7. Uetikon19:57

Next service: tomorrow 18:51 from Baden · Fri 6 Nov

Next departure 18:51 tomorrow · Baden
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
48/48 runs under 3 min
RT coverage: 48 full · 0 partial · 2 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 48
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 48 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
18:51on time on time
18:54≈ on time ≈ on time
18:58≈ on time ≈ on time
19:02 / 19:03≈ on time ≈ on time
19:04≈ on time ≈ on time
19:07≈ on time ≈ on time
19:10 / 19:11≈ on time ≈ on time
19:14≈ on time ≈ on time
19:17≈ on time ≈ +1 min
19:20 / 19:21≈ on time ≈ +1 min
19:25≈ on time ≈ +1 min
19:28 / 19:30≈ on time ≈ +1 min
19:32 / 19:33≈ on time ≈ +1 min
19:36≈ on time ≈ +1 min
19:38≈ on time ≈ +1 min
19:40≈ on time ≈ +1 min
19:42 / 19:43≈ on time ≈ +1 min
19:45≈ on time ≈ +1 min
19:47≈ on time ≈ +1 min
19:50≈ on time ≈ +1 min
19:53≈ on time ≈ +1 min
19:57on 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
Thu 5 NovUetikon 10:280 min—
Wed 4 NovUetikon 10:280 min—
Tue 3 NovUetikon 10:280 min—
Mon 2 NovUetikon 10:290 min—
Sun 1 NovUetikon 10:29+1 min—
Sat 31 OctUetikon 10:280 min—
Fri 30 OctUetikon 10:280 min—
Thu 29 OctUetikon 10:28No data—
Wed 28 OctUetikon 10:280 min—
Tue 27 OctUetikon 10:290 min—
Mon 26 OctBaden 11:010 min—
Sun 25 OctUetikon 10:28+1 min+2 min
Sat 24 OctUetikon 10:30+2 min+2 min
Fri 23 OctUetikon 10:31+3 min+3 min
Thu 22 OctUetikon 10:30+2 min+2 min
Wed 21 OctUetikon 10:27−1 min—
Tue 20 OctUetikon 10:280 min—
Mon 19 OctUetikon 10:29+1 min—
Sun 18 OctUetikon 10:290 min—
Sat 17 OctUetikon 10:280 min—
Fri 16 OctUetikon 10:280 min—
Thu 15 OctUetikon 10:27−1 min—
Wed 14 OctUetikon 10:280 min—
Tue 13 OctUetikon 10:290 min—
Mon 12 OctUetikon 10:280 min—
Sun 11 OctUetikon 10:280 min—
Sat 10 OctUetikon 10:280 min—
Fri 9 OctUetikon 10:280 min—
Thu 8 OctUetikon 10:28−1 min—
Wed 7 OctUetikon 10:27−1 min—