S6 18669 Baden – Uetikon

View line S6

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

It has not run yet today

Last recorded run: Monday 9 November +2 min

Next service: today 17:51 from Baden · Tue 10 Nov

Next departure 17:51 today · Baden
On-time · 30 days
90%
26/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
92%
44/48 runs under 3 min
RT coverage: 48 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 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

  • Fri 30 Oct Max en route +3 min · last fix heading to Uetikon +3 min
  • Tue 20 Oct Max en route +3 min · last fix heading to Uetikon +3 min
  • Wed 7 Oct Max en route +3 min · last fix heading to Uetikon +3 min
  • Thu 29 Oct Max en route +3 min · last fix heading to Uetikon +3 min

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 92% · 44
  • 3–10 min 8% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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