S26 20691 Winterthur – Bauma

View line S26

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

✓ Today’s run finished

Today it reached Bauma at 00:49 +1 min

  1. Winterthur00:13
  2. Winterthur Seen00:20
  3. Sennhof-Kyburg00:24
  4. Rikon00:30
  5. Turbenthal00:36
  6. Wila00:38
  7. Bauma00:48

Next service: tomorrow 00:13 from Winterthur · Sun 8 Nov

Next departure 00:13 tomorrow · Winterthur
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
100%
43/43 runs under 3 min
RT coverage: 43 full · 0 partial · 2 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

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

  • Early 0% · 0
  • On time 100% · 43
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 43 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
00:13on time +1 min
00:18≈ on time ≈ +1 min
00:20 / 00:21≈ on time ≈ +1 min
00:24≈ on time ≈ +1 min
00:26 / 00:27≈ on time ≈ +1 min
00:30≈ on time ≈ +1 min
00:32≈ on time ≈ +1 min
00:36≈ on time ≈ +1 min
00:38≈ on time ≈ +1 min
00:43 / 00:44≈ +1 min ≈ +2 min
00: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
Sat 7 NovBauma 00:49+1 min—
Fri 6 NovBauma 00:50+1 min—
Thu 5 NovBauma 00:49+1 min—
Wed 4 NovBauma 00:49+1 min—
Tue 3 NovBauma 00:49+1 min—
Mon 2 NovBauma 00:49+1 min—
Sun 1 NovBauma 00:51+2 min+2 min
Sat 31 OctBauma 00:51+2 min+2 min
Fri 30 OctBauma 00:490 min—
Thu 29 OctBauma 00:50+1 min—
Wed 28 OctBauma 00:50+1 min—
Tue 27 OctBauma 00:50+1 min—
Mon 26 OctBauma 00:490 min—
Sun 25 OctBauma 01:49No data—
Sat 24 OctBauma 00:51+2 min+2 min
Fri 23 OctBauma 00:50+1 min+1 min
Thu 22 OctBauma 00:49+1 min—
Wed 21 OctBauma 00:50+1 min—
Tue 20 OctBauma 00:49+1 min—
Mon 19 OctBauma 00:500 min—
Sun 18 OctBauma 00:51+1 min+1 min
Sat 17 OctBauma 00:51+1 min+1 min
Fri 16 OctBauma 00:50+1 min—
Thu 15 OctBauma 00:49No data—
Wed 14 OctBauma 00:50+1 min—
Tue 13 OctBauma 00:49+1 min—
Mon 12 OctBauma 00:50+1 min—
Sun 11 OctBauma 00:51+2 min+2 min
Sat 10 OctBauma 00:50+1 min—
Fri 9 OctBauma 00:490 min—