S6 18629 Baden – Meilen

View line S6

Baden 07:51 → Meilen 08:53 Daily 1 h 02 min · 21 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Meilen at 08:54 +1 min

  1. Baden07:51
  2. Otelfingen08:02
  3. Zürich Affoltern08:14
  4. Zürich Hardbrücke08:25
  5. Zürich Tiefenbrunnen08:36
  6. Erlenbach ZH08:45
  7. Meilen08:53

Next service: tomorrow 07:51 from Baden · Sun 8 Nov

Next departure 07:51 tomorrow · Baden
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
43/45 runs under 3 min
RT coverage: 45 full · 0 partial · 1 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: +3 min

Last 30 days

Arrival delay at Meilen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 4 Nov Max en route +5 min · last fix heading to Uetikon +5 min
  • Wed 30 Sept Max en route +3 min · last fix heading to Uetikon +3 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 93% · 42
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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