S5 18594 Rapperswil SG – Zug

View line S5

Rapperswil SG 23:59 → Zug 01:24 Daily 1 h 25 min · 21 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Zug at 01:27 +3 min

  1. Rapperswil SG23:59
  2. Bubikon00:09
  3. Zürich HB00:35
  4. Urdorf00:49
  5. Bonstetten-Wettswil00:59
  6. Knonau01:15
  7. Zug01:24

Next service: tomorrow 23:59 from Rapperswil SG · Wed 11 Nov

Next departure 23:59 tomorrow · Rapperswil SG
On-time · 30 days
93%
25/27 runs under 3 min
RT coverage: 27 full · 0 partial · 0 no data
On-time · 90 days
91%
50/55 runs under 3 min
RT coverage: 55 full · 0 partial · 5 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

  • Fri 6 Nov Max en route +5 min · last fix heading to Zug +5 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Zug +4 min
  • Sat 22 Aug Max en route +7 min · last fix heading to Zug +4 min
  • Mon 5 Oct Max en route +4 min · last fix heading to Zug +4 min
  • Tue 10 Nov Max en route +3 min · last fix heading to Zug +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 50
  • 3–10 min 9% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 88% T n=8
  • 100% W n=8
  • 100% T n=8
  • 75% F n=8
  • 90% S n=10
  • 100% S n=7

Stops and timetable

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

Last 90 days, 55 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
23:59+1 min +1 min
00:01≈ +1 min ≈ +1 min
00:06≈ +1 min ≈ +1 min
00:09≈ on time ≈ +1 min
00:14 / 00:15≈ +1 min ≈ +1 min
00:20 / 00:21≈ +1 min ≈ +1 min
00:32≈ +1 min ≈ +1 min
00:35 / 00:39≈ +1 min ≈ +1 min
00:41≈ +1 min ≈ +2 min
00:44 / 00:45≈ +1 min ≈ +2 min
00:49≈ +1 min ≈ +2 min
00:51≈ +1 min ≈ +2 min
00:55≈ +1 min ≈ +2 min
00:59≈ +1 min ≈ +2 min
01:04≈ +1 min ≈ +2 min
01:07 / 01:08≈ +1 min ≈ +2 min
01:11≈ +1 min ≈ +2 min
01:15≈ +1 min ≈ +2 min
01:18≈ +1 min ≈ +2 min
01:19≈ +1 min ≈ +2 min
01:24+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
Tue 10 NovZug 01:28+3 min+3 min
Sun 8 NovZug 01:240 min—
Sat 7 NovZug 01:240 min—
Fri 6 NovZug 01:24+5 min+5 min
Thu 5 NovZug 01:240 min—
Wed 4 NovZug 01:27+2 min+2 min
Tue 3 NovZug 01:240 min—
Mon 2 NovZug 01:27+2 min+2 min
Sat 31 OctZug 01:25+1 min+3 min
Fri 30 OctZug 01:250 min—
Thu 29 OctZug 01:28+2 min+2 min
Wed 28 OctZug 01:250 min—
Tue 27 OctZug 01:25+1 min—
Mon 26 OctZug 01:26+1 min+1 min
Sat 24 OctZug 01:26+1 min+1 min
Fri 23 OctZug 01:250 min—
Thu 22 OctZug 01:250 min—
Wed 21 OctZug 01:26+1 min—
Tue 20 OctZug 01:250 min—
Mon 19 OctZug 01:27+2 min+2 min
Sun 18 OctZug 01:27+1 min+1 min
Sat 17 OctZug 01:260 min—
Fri 16 OctZug 01:26+1 min+1 min
Thu 15 OctZug 01:28+3 min+3 min
Wed 14 OctZug 01:250 min+1 min
Tue 13 OctZug 01:25+1 min+1 min
Mon 12 OctZug 01:27+2 min+2 min
Sun 11 OctZug 01:26+1 min—
Sat 10 OctZug 01:260 min—
Fri 9 OctZug 01:29+4 min+4 min