S36 23973 Waldshut – Bülach

View line S36

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

It has not run yet today

Last recorded run: Monday 9 November No data

Next service: today 12:05 from Waldshut · Tue 10 Nov

Next departure 12:05 today · Waldshut
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
94%
30/32 runs under 3 min
RT coverage: 32 full · 0 partial · 9 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

  • Sat 31 Oct Max en route +17 min · last fix heading to Bülach +16 min
  • Mon 21 Sept Max en route +3 min · last fix heading to Bülach +3 min

Distribution · 90 days

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

  • Early 22% · 7
  • On time 72% · 23
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=2
  • 100% T n=5
  • 100% W n=6
  • 100% T n=2
  • 100% F n=5
  • 80% 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, 32 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
12:05+1 min +1 min
12:11 / 12:16≈ on time ≈ on time
12:18≈ on time ≈ +1 min
12:21≈ on time ≈ +1 min
12:24 / 12:25≈ on time ≈ +1 min
12:28≈ on time ≈ +1 min
12:31≈ on time ≈ +1 min
12:33≈ on time ≈ +1 min
12:37≈ on time ≈ +1 min
12:42≈ on time ≈ +1 min
12:46≈ 1 min early ≈ +1 min
12: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
Mon 9 NovBülach 12:54No data—
Sun 8 NovBülach 12:54−1 min—
Sat 7 NovBülach 12:53−1 min—
Fri 6 NovBülach 12:53−1 min—
Thu 5 NovBülach 12:54No data—
Wed 4 NovBülach 12:53−1 min—
Tue 3 NovBülach 12:53−1 min—
Mon 2 NovBülach 12:54No data—
Sun 1 NovBülach 12:53−1 min—
Sat 31 OctBülach 13:10+16 min+17 min
Fri 30 OctBülach 12:53−1 min—
Thu 29 OctBülach 12:54No data—
Wed 28 OctBülach 12:54−1 min—
Tue 27 OctBülach 12:550 min—
Mon 26 OctBülach 12:54No data—
Sun 25 OctBülach 12:53−1 min—
Sat 24 OctBülach 12:55+2 min+2 min
Fri 23 OctBülach 12:540 min—
Thu 22 OctBülach 12:54No data—
Wed 21 OctBülach 12:540 min—
Tue 20 OctBülach 12:540 min—
Mon 19 OctBülach 12:54No data—
Sun 18 OctBülach 12:54−1 min—
Sat 17 OctBülach 12:53−1 min—
Fri 16 OctBülach 12:54−1 min—
Thu 15 OctBülach 12:54No data—
Wed 14 OctBülach 12:53−1 min—
Tue 13 OctBülach 12:540 min—
Mon 12 OctBülach 12:54No data—
Sun 11 OctBülach 12:53−1 min—