S6 18645 Baden – Uetikon

View line S6

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

✓ Today’s run finished

Today it reached Uetikon at 12:59 +2 min

  1. Baden11:51
  2. Otelfingen Golfpark12:04
  3. Zürich Affoltern12:14
  4. Zürich HB12:28
  5. Zollikon12:38
  6. Winkel am Zürichsee12:47
  7. Uetikon12:57

Next service: tomorrow 11:51 from Baden · Wed 11 Nov

Next departure 11:51 tomorrow · Baden
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
98%
39/40 runs under 3 min
RT coverage: 40 full · 0 partial · 7 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: +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

  • Sun 1 Nov Max en route +7 min · last fix heading to Uetikon +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 39
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=7
  • 100% W n=5
  • 100% T n=2
  • 100% F n=6
  • 100% S n=7
  • 88% S n=8

Stops and timetable

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

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