S4 11447 Rapperswil SG – Sargans

View line S4

Rapperswil SG 12:37 → Sargans 14:54 Daily 2 h 17 min · 30 stops SOB

✓ Today’s run finished

Today it reached Sargans at 14:54 −1 min

  1. Rapperswil SG12:37
  2. Brunnadern-Neckertal13:05
  3. St. Gallen Haggen13:29
  4. Rorschach Stadt13:53
  5. St. Margrethen SG14:06
  6. Oberriet SG14:25
  7. Sargans14:54

Next service: tomorrow 12:37 from Rapperswil SG · Sat 7 Nov

Next departure 12:37 tomorrow · Rapperswil SG
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 4 no data
On-time · 90 days
100%
41/41 runs under 3 min
RT coverage: 41 full · 0 partial · 4 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Sargans, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 49% · 20
  • On time 51% · 21
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=6
  • 100% W n=5
  • 100% T n=4
  • 100% F n=8
  • 100% S n=7
  • 100% S n=7

Stops and timetable

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

Last 90 days, 41 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:37on time on time
12:47 / 12:48≈ on time ≈ on time
12:51≈ 1 min early ≈ on time
12:59≈ 1 min early ≈ on time
13:01≈ 1 min early ≈ on time
13:05≈ 1 min early ≈ on time
13:08≈ 1 min early ≈ on time
13:14 / 13:15≈ 1 min early ≈ on time
13:18≈ 1 min early ≈ on time
13:23 / 13:24≈ 1 min early ≈ on time
13:29≈ 1 min early ≈ on time
13:33 / 13:38≈ 1 min early ≈ on time
13:41≈ 1 min early ≈ on time
13:46≈ 1 min early ≈ on time
13:51≈ 1 min early ≈ on time
13:53≈ 1 min early ≈ on time
13:56≈ 1 min early ≈ on time
13:58≈ 1 min early ≈ on time
14:02≈ 1 min early ≈ on time
14:06 / 14:07≈ 1 min early ≈ on time
14:09≈ 1 min early ≈ on time
14:13≈ 1 min early ≈ on time
14:16≈ 1 min early ≈ on time
14:20≈ 1 min early ≈ on time
14:25≈ 1 min early ≈ on time
14:29≈ 1 min early ≈ on time
14:33≈ 1 min early ≈ on time
14:40≈ 1 min early ≈ on time
14:43≈ 1 min early ≈ on time
14:541 min early on time

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 6 NovSargans 14:54−1 min—
Thu 5 NovSargans 14:54No data—
Wed 4 NovSargans 14:54−1 min—
Tue 3 NovSargans 14:53−2 min—
Mon 2 NovSargans 14:54No data—
Sun 1 NovSargans 14:540 min—
Sat 31 OctSargans 14:550 min—
Fri 30 OctSargans 14:54−1 min—
Thu 29 OctSargans 14:54−2 min—
Wed 28 OctSargans 14:54−2 min—
Tue 27 OctSargans 14:57+1 min+1 min
Mon 26 OctSargans 14:55No data—
Sun 25 OctSargans 14:550 min—
Sat 24 OctSargans 14:54−1 min—
Fri 23 OctSargans 14:53−1 min—
Thu 22 OctSargans 14:56+1 min—
Wed 21 OctSargans 14:56+1 min+1 min
Tue 20 OctSargans 14:53−2 min—
Mon 19 OctSargans 14:540 min—
Sun 18 OctSargans 14:56+1 min+1 min
Sat 17 OctSargans 14:54−1 min—
Fri 16 OctSargans 14:53−2 min—
Thu 15 OctSargans 14:54No data—
Wed 14 OctSargans 14:53−2 min—
Tue 13 OctSargans 14:54−1 min—
Mon 12 OctSargans 14:550 min—
Sun 11 OctSargans 14:550 min—
Sat 10 OctSargans 14:55−1 min—
Fri 9 OctSargans 14:54−1 min—
Thu 8 OctSargans 14:54−1 min—