S6 18651 Baden – Uetikon

View line S6

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

✓ Today’s run finished

Today it reached Uetikon at 14:27 0 min

  1. Baden13:21
  2. Otelfingen Golfpark13:34
  3. Zürich Affoltern13:44
  4. Zürich HB13:58
  5. Zollikon14:08
  6. Winkel am Zürichsee14:17
  7. Uetikon14:27

Next service: tomorrow 13:21 from Baden · Sat 7 Nov

Next departure 13:21 tomorrow · Baden
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 9 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: +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

  • Tue 20 Oct Max en route +3 min · last fix heading to Uetikon +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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