S17 12341 Rapperswil SG – Sargans

View line S17

Rapperswil SG 11:03 → Sargans 11:57 Daily 0 h 54 min · 14 stops SOB

Running now · updated 11:46

Position estimated from the timetable

Between Walenstadt and Flums 0 min

Estimated arrival at Sargans 11:57 · 69 km/h

  1. Rapperswil SG11:03
  2. Schmerikon11:11
  3. Benken SG11:18
  4. Mühlehorn11:34
  5. Walenstadt11:46
  6. Flums11:49
  7. Sargans11:57

Today it is running worse than usual: typical arrival delay is 0 min; 100% of the last 23 runs arrived on time.

On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 22 full · 1 partial · 7 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 32 full · 1 partial · 8 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

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

  • Early 0% · 0
  • On time 100% · 33
  • 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=6
  • 100% W n=6
  • 100% T n=2
  • 100% F n=6
  • 100% S n=5
  • 100% S n=7

Stops and timetable

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

Last 90 days, 33 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 10Today
11:03on time on timePassed
11:05≈ on time ≈ on timePassed
11:11≈ on time ≈ on timePassed
11:14 / 11:16≈ on time ≈ on timePassed
11:18≈ on time ≈ on timePassed
11:23≈ on time ≈ on timePassed
11:27 / 11:28≈ on time ≈ on timePassed
11:34≈ on time ≈ on timePassed
11:37≈ on time ≈ on timePassed
11:41≈ on time ≈ on timePassed
11:46≈ on time ≈ on timePassed
11:49≈ on time ≈ on timeNext
11:54≈ on time ≈ on time
11:57on time 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
Wed 11 NovWalenstadt 11:44Partial coverage0 min—
Tue 10 NovSargans 11:580 min—
Mon 9 NovSargans 11:58No data—
Sun 8 NovSargans 11:58−1 min—
Sat 7 NovSargans 11:580 min—
Fri 6 NovSargans 11:580 min—
Thu 5 NovSargans 11:58No data—
Wed 4 NovSargans 11:580 min—
Tue 3 NovSargans 11:580 min—
Mon 2 NovSargans 11:58No data—
Sun 1 NovSargans 11:57−1 min—
Sat 31 OctSargans 11:57−1 min—
Fri 30 OctSargans 11:57−1 min—
Thu 29 OctSargans 11:58No data—
Wed 28 OctSargans 11:580 min—
Tue 27 OctSargans 11:59+1 min—
Mon 26 OctSargans 11:59No data—
Sun 25 OctSargans 11:57−1 min—
Sat 24 OctSargans 11:57−1 min—
Fri 23 OctSargans 11:570 min—
Thu 22 OctSargans 11:580 min—
Wed 21 OctSargans 12:00+2 min+2 min
Tue 20 OctSargans 11:58−1 min—
Mon 19 OctSargans 11:58No data—
Sun 18 OctSargans 11:58−1 min—
Sat 17 OctSargans 11:58−1 min—
Fri 16 OctSargans 11:570 min—
Thu 15 OctSargans 11:58No data—
Wed 14 OctSargans 11:57−1 min—
Tue 13 OctSargans 11:58−1 min—