S6 18659 Baden – Uetikon

View line S6

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

✓ Today’s run finished

Today it reached Uetikon at 16:29 +2 min

  1. Baden15:21
  2. Otelfingen Golfpark15:34
  3. Zürich Affoltern15:44
  4. Zürich HB15:58
  5. Zollikon16:08
  6. Winkel am Zürichsee16:17
  7. Uetikon16:27

Next service: tomorrow 15:21 from Baden · Fri 13 Nov

Next departure 15:21 tomorrow · Baden
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
44/46 runs under 3 min
RT coverage: 46 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Mon 5 Oct Max en route +5 min · last fix heading to Uetikon +5 min
  • Fri 21 Aug Max en route +5 min · last fix heading to Meilen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 44
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 46 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
15:21on time on time
15:24≈ on time ≈ on time
15:28≈ on time ≈ +1 min
15:32 / 15:33≈ on time ≈ +1 min
15:34≈ on time ≈ +1 min
15:37≈ on time ≈ +1 min
15:40 / 15:41≈ on time ≈ +1 min
15:44≈ on time ≈ +1 min
15:47≈ on time ≈ +1 min
15:50 / 15:51≈ on time ≈ +1 min
15:55≈ on time ≈ +1 min
15:58 / 16:00≈ on time ≈ +1 min
16:02 / 16:03≈ on time ≈ +1 min
16:06≈ on time ≈ +1 min
16:08≈ on time ≈ +2 min
16:10≈ on time ≈ +2 min
16:12 / 16:13≈ on time ≈ +2 min
16:15≈ on time ≈ +2 min
16:17≈ on time ≈ +2 min
16:20≈ on time ≈ +2 min
16:23≈ on time ≈ +2 min
16:27on time +2 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 12 NovUetikon 16:29+2 min+2 min
Wed 11 NovUetikon 16:280 min—
Tue 10 NovUetikon 16:280 min—
Mon 9 NovUetikon 16:280 min—
Sun 8 NovMeilen 16:27+3 min+3 min
Sat 7 NovMeilen 16:24+1 min—
Fri 6 NovUetikon 16:29+2 min+2 min
Thu 5 NovUetikon 16:29+1 min—
Wed 4 NovUetikon 16:280 min—
Tue 3 NovUetikon 16:29+1 min—
Mon 2 NovUetikon 16:29+2 min+2 min
Sun 1 NovUetikon 16:280 min—
Sat 31 OctUetikon 16:280 min—
Fri 30 OctUetikon 16:29+1 min—
Thu 29 OctUetikon 16:29+1 min+1 min
Wed 28 OctUetikon 16:290 min—
Tue 27 OctUetikon 16:280 min—
Mon 26 OctUetikon 16:29+1 min—
Sun 25 OctUetikon 16:28+1 min—
Sat 24 OctUetikon 16:280 min—
Fri 23 OctUetikon 16:28+1 min—
Thu 22 OctUetikon 16:280 min—
Wed 21 OctUetikon 16:280 min—
Tue 20 OctUetikon 16:28+2 min+2 min
Mon 19 OctUetikon 16:280 min—
Sun 18 OctUetikon 16:280 min—
Sat 17 OctUetikon 16:280 min—
Fri 16 OctUetikon 16:290 min—
Thu 15 OctUetikon 16:290 min—
Wed 14 OctUetikon 16:280 min—