S24 20441 Schaffhausen → Zug

View line S24

Schaffhausen 10:15 → Zug 11:56 Daily 1 h 41 min · 21 stops SBB CFF FFS

S24 20441 Schaffhausen–Zug: final delay under 3 min on 27 of its 28 runs with data in the last 30 days (96%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 22:04 (GMT+1).

✓ Today’s run finished

Today it reached Zug at 11:57 +1 min

  1. Schaffhausen10:15
  2. Winterthur10:42
  3. Zürich Flughafen11:02
  4. Zürich HB11:16
  5. Zürich Wollishofen11:29
  6. Oberrieden Dorf11:41
  7. Zug11:56

Next service: tomorrow 10:15 from Schaffhausen · Sun 22 Nov

Next departure 10:15 tomorrow · Schaffhausen
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
96%
54/56 runs under 3 min
RT coverage: 56 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 Zug, 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 +4 min · last fix heading to Zug +4 min
  • Wed 23 Sept Max en route +3 min · last fix heading to Zug +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 54
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 78% W n=9
  • 100% T n=6
  • 100% F n=9
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 56 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
10:15on time on time
10:18≈ on time ≈ on time
10:30≈ on time ≈ +1 min
10:42 / 10:45≈ on time ≈ +1 min
10:49≈ on time ≈ +1 min
10:53≈ on time ≈ +1 min
10:57≈ on time ≈ +1 min
11:02 / 11:04≈ on time ≈ +1 min
11:08 / 11:09≈ on time ≈ +1 min
11:11≈ on time ≈ +1 min
11:16 / 11:21≈ on time ≈ +2 min
11:24≈ on time ≈ +2 min
11:27≈ on time ≈ +2 min
11:29≈ on time ≈ +2 min
11:33≈ on time ≈ +2 min
11:35≈ on time ≈ +2 min
11:38≈ on time ≈ +2 min
11:41≈ on time ≈ +2 min
11:44≈ on time ≈ +2 min
11:52≈ +1 min ≈ +2 min
11:56+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 21 NovZug 11:57+1 min—
Fri 20 NovZug 11:570 min—
Thu 19 NovZug 11:57No data—
Wed 18 NovZug 11:59+4 min+4 min
Tue 17 NovZug 11:59+2 min+2 min
Mon 16 NovZug 11:570 min—
Sun 15 NovZug 11:570 min—
Sat 14 NovZug 11:570 min—
Fri 13 NovZug 11:580 min—
Thu 12 NovZug 11:570 min—
Wed 11 NovZug 11:58+1 min+1 min
Tue 10 NovZug 11:58+1 min+1 min
Mon 9 NovZug 11:570 min—
Sun 8 NovZug 11:58+1 min—
Sat 7 NovZug 11:570 min—
Fri 6 NovZug 11:59+2 min+2 min
Thu 5 NovZug 11:570 min—
Wed 4 NovZug 11:58+1 min+1 min
Tue 3 NovZug 11:58+1 min—
Mon 2 NovZug 11:570 min—
Sun 1 NovZug 11:58+2 min+2 min
Sat 31 OctZug 11:58+1 min+1 min
Fri 30 OctZug 11:58+1 min—
Thu 29 OctZug 11:57No data—
Wed 28 OctZug 11:59+2 min+2 min
Tue 27 OctZug 11:58+1 min—
Mon 26 OctZug 11:580 min—
Sun 25 OctZug 11:59+2 min+2 min
Sat 24 OctZug 11:570 min—
Fri 23 OctZug 11:59+3 min+3 min