S24 20445 Schaffhausen – Zug

View line S24

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

✓ Today’s run finished

Today it reached Zug at 12:56 0 min

  1. Schaffhausen11:15
  2. Winterthur11:42
  3. Zürich Flughafen12:02
  4. Zürich HB12:16
  5. Zürich Wollishofen12:29
  6. Oberrieden Dorf12:41
  7. Zug12:56

Next service: tomorrow 11:15 from Schaffhausen · Sat 21 Nov

Next departure 11:15 tomorrow · Schaffhausen
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
95%
42/44 runs under 3 min
RT coverage: 44 full · 0 partial · 12 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: +3 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

  • Fri 6 Nov Max en route +4 min · last fix heading to Zug +4 min
  • Tue 17 Nov Max en route +3 min · last fix heading to Zug +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 42
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 88% T n=8
  • 100% W n=8
  • 100% T n=2
  • 89% F n=9
  • 100% S n=9
  • 100% S n=7

Stops and timetable

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

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