S24 20449 Schaffhausen → Zug

View line S24

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

S24 20449 Schaffhausen–Zug: final delay under 3 min on 23 of its 23 runs with data in the last 30 days (100%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 23:06 (GMT+1).

✓ Today’s run finished

Today it reached Zug at 13:59 +3 min

  1. Schaffhausen12:15
  2. Winterthur12:42
  3. Zürich Flughafen13:02
  4. Zürich HB13:16
  5. Zürich Wollishofen13:29
  6. Oberrieden Dorf13:41
  7. Zug13:56

Next service: tomorrow 12:15 from Schaffhausen · Mon 23 Nov

Next departure 12:15 tomorrow · Schaffhausen
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
93%
41/44 runs under 3 min
RT coverage: 44 full · 0 partial · 11 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

  • Sun 18 Oct Max en route +10 min · last fix heading to Zug +10 min
  • Fri 23 Oct Max en route +4 min · last fix heading to Zug +4 min
  • Mon 31 Aug Max en route +3 min · last fix heading to Baar +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 93% · 41
  • 3–10 min 7% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=7
  • 100% W n=7
  • 100% T n=3
  • 86% F n=7
  • 100% S n=8
  • 88% S n=8

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