S26 20663 Winterthur → Rüti ZH

View line S26

Winterthur 17:13 → Rüti ZH 18:16 Daily 1 h 03 min · 17 stops Thurbo

S26 20663 Winterthur–Rüti ZH: final delay under 3 min on 26 of its 29 runs with data in the last 30 days (90%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 11:53 (GMT+1).

It has not run yet today

Last recorded run: Friday 20 November +1 min

Next service: today 17:13 from Winterthur · Sat 21 Nov

Next departure 17:13 today · Winterthur
On-time · 30 days
90%
26/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
94%
45/48 runs under 3 min
RT coverage: 48 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Rüti ZH, in minutes. One bar per run.

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

Worst days

  • Wed 18 Nov Max en route +6 min · last fix heading to Rüti ZH +6 min
  • Thu 12 Nov Max en route +5 min · last fix heading to Rüti ZH +5 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Rüti ZH +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 45
  • 3–10 min 6% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 48 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
17:13on time on time
17:18≈ on time ≈ on time
17:20 / 17:21≈ on time ≈ on time
17:24≈ on time ≈ on time
17:26 / 17:27≈ on time ≈ +1 min
17:30≈ on time ≈ +1 min
17:32≈ on time ≈ +1 min
17:36≈ on time ≈ +1 min
17:38≈ on time ≈ +1 min
17:43 / 17:44≈ on time ≈ +1 min
17:48 / 17:50≈ on time ≈ +1 min
17:54≈ on time ≈ +2 min
17:58 / 17:59≈ on time ≈ +2 min
18:01≈ on time ≈ +2 min
18:07 / 18:08≈ on time ≈ +2 min
18:13≈ on time ≈ +2 min
18:16on time +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 20 NovRüti ZH 18:17+1 min—
Thu 19 NovRüti ZH 18:19+2 min+2 min
Wed 18 NovRüti ZH 18:23+6 min+6 min
Tue 17 NovRüti ZH 18:18+1 min—
Mon 16 NovRüti ZH 18:17+1 min—
Sun 15 NovRüti ZH 18:170 min—
Sat 14 NovRüti ZH 18:170 min—
Fri 13 NovRüti ZH 18:170 min—
Thu 12 NovRüti ZH 18:22+5 min+5 min
Wed 11 NovRüti ZH 18:18+1 min—
Tue 10 NovRüti ZH 18:170 min—
Mon 9 NovRüti ZH 18:18+2 min+2 min
Sun 8 NovRüti ZH 18:170 min—
Sat 7 NovRüti ZH 18:170 min—
Fri 6 NovRüti ZH 18:19+3 min+3 min
Thu 5 NovRüti ZH 18:170 min—
Wed 4 NovRüti ZH 18:19+3 min+3 min
Tue 3 NovRüti ZH 18:180 min—
Mon 2 NovRüti ZH 18:19+2 min+2 min
Sun 1 NovRüti ZH 18:170 min—
Sat 31 OctRüti ZH 18:170 min—
Fri 30 OctRüti ZH 18:18+1 min+1 min
Thu 29 OctRüti ZH 18:19+1 min+1 min
Wed 28 OctRüti ZH 18:18+1 min—
Tue 27 OctRüti ZH 18:18+1 min—
Mon 26 OctRüti ZH 18:170 min—
Sun 25 OctRüti ZH 18:17+1 min—
Sat 24 OctRüti ZH 18:18+1 min—
Fri 23 OctRüti ZH 18:19+2 min+2 min
Thu 22 OctRüti ZH 18:170 min—