S27 20767 Waldshut – Wettingen

View line S27

Waldshut 16:35 → Wettingen 17:08 Daily 0 h 33 min · 8 stops SBB CFF FFS

It has not run yet today

Last recorded run: Thursday 5 November +2 min

Next service: today 16:35 from Waldshut · Fri 6 Nov

Next departure 16:35 today · Waldshut
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
98%
39/40 runs under 3 min
RT coverage: 40 full · 0 partial · 0 no data
Typical delay
+1min
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 Wettingen, 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 27 Oct Max en route +4 min · last fix heading to Wettingen +3 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 95% · 38
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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
16:35+1 min +1 min
16:41 / 16:44≈ +1 min ≈ +1 min
16:46≈ +1 min ≈ +1 min
16:48 / 16:49≈ +1 min ≈ +1 min
16:53≈ +1 min ≈ +1 min
16:58≈ +1 min ≈ +1 min
17:03 / 17:04≈ +1 min ≈ +2 min
17:08+1 min +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
Thu 5 NovWettingen 17:09+2 min+2 min
Wed 4 NovWettingen 17:09+1 min—
Tue 3 NovWettingen 17:12+2 min+2 min
Mon 2 NovWettingen 17:09+1 min+3 min
Sun 1 NovBaden 17:04+1 min+1 min
Sat 31 OctBaden 17:040 min—
Fri 30 OctWettingen 17:10+1 min+2 min
Thu 29 OctWettingen 17:090 min—
Wed 28 OctWettingen 17:100 min+1 min
Tue 27 OctWettingen 17:12+3 min+4 min
Mon 26 OctWettingen 17:11+2 min+2 min
Sun 25 OctBaden 17:04+1 min—
Sat 24 OctBaden 17:05+1 min+1 min
Fri 23 OctWettingen 17:10+1 min+2 min
Thu 22 OctWettingen 17:11+2 min+2 min
Wed 21 OctWettingen 17:12+2 min+2 min
Tue 20 OctWettingen 17:10+1 min+2 min
Mon 19 OctWettingen 17:090 min—
Sun 18 OctBaden 17:05+1 min—
Sat 17 OctBaden 17:05+1 min—
Fri 16 OctWettingen 17:11+1 min+2 min
Thu 15 OctWettingen 17:090 min—
Wed 14 OctWettingen 17:090 min—
Tue 13 OctWettingen 17:090 min—
Mon 12 OctWettingen 17:10+1 min+2 min
Sun 11 OctBaden 17:040 min—
Sat 10 OctBaden 17:040 min—
Fri 9 OctWettingen 17:10+1 min—
Thu 8 OctWettingen 17:090 min—
Wed 7 OctWettingen 17:10+1 min—