S36 23981 Waldshut – Bülach

View line S36

Waldshut 16:05 → Bülach 16:53 Daily 0 h 48 min · 12 stops Thurbo

✓ Today’s run finished

Today it reached Bülach at 16:53 0 min

  1. Waldshut16:05
  2. Koblenz Dorf16:18
  3. Bad Zurzach16:24
  4. Mellikon16:31
  5. Rümikon AG16:33
  6. Zweidlen16:42
  7. Bülach16:53

Next service: tomorrow 16:05 from Waldshut · Sun 8 Nov

Next departure 16:05 tomorrow · Waldshut
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
97%
37/38 runs under 3 min
RT coverage: 38 full · 0 partial · 1 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Bülach, in minutes. One bar per run.

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

Worst days

  • Mon 17 Aug Max en route +5 min · last fix heading to Bülach +5 min

Distribution · 90 days

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

  • Early 45% · 17
  • On time 53% · 20
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 38 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:05+1 min +1 min
16:11 / 16:16≈ on time ≈ +1 min
16:18≈ on time ≈ +1 min
16:21≈ on time ≈ +1 min
16:24 / 16:25≈ on time ≈ +1 min
16:28≈ on time ≈ +1 min
16:31≈ on time ≈ +1 min
16:33≈ on time ≈ +1 min
16:37≈ on time ≈ +1 min
16:42≈ 1 min early ≈ +1 min
16:46≈ 1 min early ≈ +1 min
16:531 min early +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
Sat 7 NovBülach 16:540 min—
Fri 6 NovBülach 16:53−1 min—
Thu 5 NovBülach 16:54+1 min—
Wed 4 NovBülach 16:540 min—
Tue 3 NovBülach 16:53−1 min—
Mon 2 NovBülach 16:53−1 min—
Sun 1 NovBülach 16:53−1 min—
Sat 31 OctBülach 16:53−1 min—
Fri 30 OctBülach 16:56+2 min+2 min
Thu 29 OctBülach 16:53−1 min—
Wed 28 OctBülach 16:540 min—
Tue 27 OctBülach 16:55+1 min—
Mon 26 OctBülach 16:53−2 min—
Sun 25 OctBülach 16:52−1 min—
Sat 24 OctBülach 16:52−2 min—
Fri 23 OctBülach 16:53−1 min—
Thu 22 OctBülach 16:54−1 min—
Wed 21 OctBülach 16:540 min—
Tue 20 OctBülach 16:53−1 min—
Mon 19 OctBülach 16:53−1 min—
Sun 18 OctBülach 16:52−1 min—
Sat 17 OctBülach 16:53−1 min—
Fri 16 OctBülach 16:550 min—
Thu 15 OctBülach 16:53−1 min—
Wed 14 OctBülach 16:53−1 min—
Tue 13 OctBülach 16:53−1 min—
Mon 12 OctBülach 16:53−1 min—
Sun 11 OctBülach 16:52−2 min—
Sat 10 OctBülach 16:53−1 min—
Fri 9 OctBülach 16:54No data—