S36 23971 Waldshut – Bülach

View line S36

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

✓ Today’s run finished

Today it reached Bülach at 11:53 −1 min

  1. Waldshut11:05
  2. Koblenz Dorf11:18
  3. Bad Zurzach11:24
  4. Mellikon11:31
  5. Rümikon AG11:33
  6. Zweidlen11:42
  7. Bülach11:53

Next service: tomorrow 11:05 from Waldshut · Sat 14 Nov

Next departure 11:05 tomorrow · Waldshut
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
100%
37/37 runs under 3 min
RT coverage: 37 full · 0 partial · 8 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
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

Distribution · 90 days

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

  • Early 41% · 15
  • On time 59% · 22
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 37 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
11:05+1 min +1 min
11:11 / 11:16≈ on time ≈ on time
11:18≈ on time ≈ on time
11:21≈ on time ≈ on time
11:24 / 11:25≈ on time ≈ on time
11:28≈ on time ≈ on time
11:31≈ on time ≈ on time
11:33≈ on time ≈ on time
11:37≈ on time ≈ on time
11:42≈ on time ≈ on time
11:46≈ 1 min early ≈ on time
11:531 min early on time

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
Fri 13 NovBülach 11:53−1 min—
Thu 12 NovBülach 11:54No data—
Wed 11 NovBülach 11:53−1 min—
Tue 10 NovBülach 11:530 min—
Mon 9 NovBülach 11:54No data—
Sun 8 NovBülach 11:53−1 min—
Sat 7 NovBülach 11:52−2 min—
Fri 6 NovBülach 11:540 min—
Thu 5 NovBülach 11:54No data—
Wed 4 NovBülach 11:53−1 min—
Tue 3 NovBülach 11:54−1 min+1 min
Mon 2 NovBülach 11:54+1 min—
Sun 1 NovBülach 11:53−1 min—
Sat 31 OctBülach 11:53−1 min—
Fri 30 OctBülach 11:540 min—
Thu 29 OctBülach 11:54No data—
Wed 28 OctBülach 11:540 min—
Tue 27 OctBülach 11:55+1 min—
Mon 26 OctBülach 11:55No data—
Sun 25 OctBülach 11:52−1 min—
Sat 24 OctBülach 11:53−1 min—
Fri 23 OctBülach 11:53−1 min—
Thu 22 OctBülach 11:54No data—
Wed 21 OctBülach 11:540 min—
Tue 20 OctBülach 11:54−1 min—
Mon 19 OctBülach 11:54No data—
Sun 18 OctBülach 11:53−2 min—
Sat 17 OctBülach 11:53−1 min—
Fri 16 OctBülach 11:52−1 min—
Thu 15 OctBülach 11:54No data—