S4 11443 Rapperswil SG – Sargans

View line S4

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

✓ Today’s run finished

Today it reached Sargans at 13:54 0 min

  1. Rapperswil SG11:37
  2. Brunnadern-Neckertal12:05
  3. St. Gallen Haggen12:29
  4. Rorschach Stadt12:53
  5. St. Margrethen SG13:06
  6. Oberriet SG13:25
  7. Sargans13:54

Next service: tomorrow 11:37 from Rapperswil SG · Sat 21 Nov

Next departure 11:37 tomorrow · Rapperswil SG
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
100%
38/38 runs under 3 min
RT coverage: 38 full · 0 partial · 11 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: 0 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

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

  • Early 50% · 19
  • On time 50% · 19
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=7
  • 100% W n=7
  • 100% T n=2
  • 100% F n=8
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 38 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:37on time on time
11:47 / 11:48≈ 1 min early ≈ on time
11:51≈ 1 min early ≈ on time
11:59≈ 1 min early ≈ on time
12:01≈ 1 min early ≈ on time
12:05≈ 1 min early ≈ on time
12:08≈ 1 min early ≈ on time
12:14 / 12:15≈ 1 min early ≈ on time
12:18≈ 1 min early ≈ on time
12:23 / 12:24≈ 1 min early ≈ on time
12:29≈ 1 min early ≈ on time
12:33 / 12:38≈ 1 min early ≈ on time
12:41≈ 1 min early ≈ on time
12:46≈ 1 min early ≈ on time
12:51≈ 1 min early ≈ on time
12:53≈ 1 min early ≈ on time
12:56≈ 1 min early ≈ on time
12:58≈ 1 min early ≈ on time
13:02≈ 1 min early ≈ on time
13:06 / 13:07≈ 1 min early ≈ on time
13:09≈ 1 min early ≈ on time
13:13≈ 1 min early ≈ on time
13:16≈ 1 min early ≈ on time
13:20≈ 1 min early ≈ on time
13:25≈ 1 min early ≈ on time
13:29≈ 1 min early ≈ on time
13:33≈ 1 min early ≈ on time
13:40≈ 1 min early ≈ on time
13:43≈ 1 min early ≈ on time
13: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 20 NovSargans 13:540 min—
Thu 19 NovSargans 13:54No data—
Wed 18 NovSargans 13:53−1 min—
Tue 17 NovSargans 13:54−2 min—
Mon 16 NovSargans 13:54No data—
Sun 15 NovSargans 13:540 min—
Sat 14 NovSargans 13:54−1 min—
Fri 13 NovSargans 13:54−1 min—
Thu 12 NovSargans 13:54No data—
Wed 11 NovSargans 13:54−1 min—
Tue 10 NovSargans 13:54−1 min—
Mon 9 NovSargans 13:54No data—
Sun 8 NovSargans 13:54−1 min—
Sat 7 NovSargans 13:54−1 min—
Fri 6 NovSargans 13:540 min—
Thu 5 NovSargans 13:54No data—
Wed 4 NovSargans 13:54−1 min—
Tue 3 NovSargans 13:54−2 min—
Mon 2 NovSargans 13:54No data—
Sun 1 NovSargans 13:53−2 min—
Sat 31 OctSargans 13:54−1 min—
Fri 30 OctSargans 13:54−1 min—
Thu 29 OctSargans 13:55No data—
Wed 28 OctSargans 13:54−1 min—
Tue 27 OctSargans 13:54−1 min—
Mon 26 OctSargans 13:55No data—
Sun 25 OctSargans 13:57+2 min+2 min
Sat 24 OctSargans 13:54−1 min—
Fri 23 OctSargans 13:54−1 min—
Thu 22 OctSargans 13:55No data—