S6 18677 Baden – Uetikon

View line S6

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

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 19:51 from Baden · Thu 5 Nov

Next departure 19:51 today · Baden
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
96%
48/50 runs under 3 min
RT coverage: 50 full · 0 partial · 1 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

  • Fri 9 Oct Max en route +4 min · last fix heading to Uetikon +4 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Uetikon +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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