S17 12333 Rapperswil SG → Sargans

View line S17

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

S17 12333 Rapperswil SG–Sargans: final delay under 3 min on 28 of its 28 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. Expected at Sargans: 09:58. TrainsRadar data as of 22 Nov 2026, 09:58 (GMT+1).

Running now · updated 09:58

Position estimated from the timetable

Between Mels and Sargans +1 min

Estimated arrival at Sargans 09:58 · 34 km/h

  1. Rapperswil SG09:03
  2. Schmerikon09:11
  3. Benken SG09:18
  4. Mühlehorn09:34
  5. Unterterzen09:41
  6. Mels09:54
  7. Sargans09:57

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

On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
100%
56/56 runs under 3 min
RT coverage: 56 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

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

  • Early 0% · 0
  • On time 100% · 56
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 56 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
09:03on time on timePassed
09:05≈ on time ≈ on timePassed
09:11≈ on time ≈ on timePassed
09:14 / 09:16≈ on time ≈ on timePassed
09:18≈ on time ≈ on timePassed
09:23≈ on time ≈ on timePassed
09:27 / 09:28≈ on time ≈ on timePassed
09:34≈ on time ≈ on timePassed
09:37≈ on time ≈ on timePassed
09:41≈ on time ≈ on timePassed
09:46≈ on time ≈ on timePassed
09:49≈ on time ≈ on timePassed
09:54≈ on time ≈ on timePassed
09:57on time +1 minNext

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 NovSargans 09:540 min—
Sat 21 NovSargans 09:59+1 min—
Fri 20 NovSargans 09:580 min—
Thu 19 NovSargans 09:58No data—
Wed 18 NovSargans 09:57−1 min—
Tue 17 NovSargans 09:58+1 min—
Mon 16 NovSargans 09:570 min—
Sun 15 NovSargans 09:580 min—
Sat 14 NovSargans 09:580 min—
Fri 13 NovSargans 09:580 min—
Thu 12 NovSargans 09:58−1 min—
Wed 11 NovSargans 09:580 min—
Tue 10 NovSargans 09:57−1 min—
Mon 9 NovSargans 09:57−1 min—
Sun 8 NovSargans 09:580 min—
Sat 7 NovSargans 09:57−1 min—
Fri 6 NovSargans 09:59+2 min+2 min
Thu 5 NovSargans 09:57−1 min—
Wed 4 NovSargans 09:57−1 min—
Tue 3 NovSargans 09:57−1 min—
Mon 2 NovSargans 09:580 min—
Sun 1 NovSargans 09:580 min—
Sat 31 OctSargans 09:57−1 min—
Fri 30 OctSargans 09:580 min—
Thu 29 OctSargans 09:58No data—
Wed 28 OctSargans 09:580 min—
Tue 27 OctSargans 09:58−1 min—
Mon 26 OctUznach 11:010 min—
Sun 25 OctSargans 09:580 min—
Sat 24 OctSargans 09:580 min—