S6 18647 Baden – Uetikon

View line S6

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

✓ Today’s run finished

Today it reached Uetikon at 13:28 +1 min

  1. Baden12:21
  2. Otelfingen Golfpark12:34
  3. Zürich Affoltern12:44
  4. Zürich HB12:58
  5. Zollikon13:08
  6. Winkel am Zürichsee13:17
  7. Uetikon13:27

Next service: tomorrow 12:21 from Baden · Sat 14 Nov

Next departure 12:21 tomorrow · Baden
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 11 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 34 full · 0 partial · 13 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

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

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

On-time by weekday

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

Stops and timetable

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

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