S26 20683 Winterthur – Bauma

View line S26

Winterthur 22:13 → Bauma 22:48 Daily 0 h 35 min · 11 stops Thurbo

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 22:13 from Winterthur · Sat 7 Nov

Next departure 22:13 today · Winterthur
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
100%
40/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 Bauma, 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

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

  • Early 3% · 1
  • On time 98% · 39
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (11 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
22:13on time on time
22:18≈ on time ≈ on time
22:20 / 22:21≈ on time ≈ +1 min
22:24≈ on time ≈ +1 min
22:26 / 22:27≈ +1 min ≈ +1 min
22:30≈ +1 min ≈ +1 min
22:32≈ +1 min ≈ +1 min
22:36≈ +1 min ≈ +1 min
22:38≈ +1 min ≈ +1 min
22:43 / 22:44≈ +1 min ≈ +2 min
22:48+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
Fri 6 NovBauma 22:49+1 min—
Thu 5 NovBauma 22:48+1 min—
Wed 4 NovBauma 22:490 min—
Tue 3 NovBauma 22:49+1 min—
Mon 2 NovBauma 22:49+1 min+1 min
Sun 1 NovBauma 22:49+1 min+1 min
Sat 31 OctBauma 22:51+2 min+2 min
Fri 30 OctBauma 22:50+1 min+1 min
Thu 29 OctBauma 22:51+2 min+2 min
Wed 28 OctBauma 22:50+1 min+1 min
Tue 27 OctBauma 22:50+1 min+1 min
Mon 26 OctBauma 22:51+1 min+1 min
Sun 25 OctBauma 22:50+1 min+1 min
Sat 24 OctBauma 22:51+2 min+2 min
Fri 23 OctBauma 22:50+1 min+1 min
Thu 22 OctBauma 22:51+2 min+2 min
Wed 21 OctBauma 22:50+1 min+1 min
Tue 20 OctBauma 22:51+2 min+2 min
Mon 19 OctBauma 22:50+1 min+1 min
Sun 18 OctBauma 22:51+2 min+2 min
Sat 17 OctBauma 22:50+2 min+2 min
Fri 16 OctBauma 22:51+2 min+2 min
Thu 15 OctBauma 22:51+2 min+2 min
Wed 14 OctBauma 22:51+1 min+1 min
Tue 13 OctBauma 22:50+1 min+1 min
Mon 12 OctBauma 22:50+1 min+1 min
Sun 11 OctBauma 22:51+2 min+2 min
Sat 10 OctBauma 22:51+1 min+1 min
Fri 9 OctBauma 22:51+1 min+1 min
Thu 8 OctBauma 22:52+3 min+3 min