S17 12345 Rapperswil SG – Sargans

View line S17

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

✓ Today’s run finished

Today, last fix heading to Sargans at 12:58 No data

  1. Rapperswil SG12:03
  2. Schmerikon12:11
  3. Benken SG12:18
  4. Mühlehorn12:34
  5. Unterterzen12:41
  6. Flums12:49
  7. Sargans12:57

Next service: tomorrow 12:03 from Rapperswil SG · Fri 20 Nov

Next departure 12:03 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%
35/35 runs under 3 min
RT coverage: 35 full · 0 partial · 12 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

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

  • Early 0% · 0
  • On time 100% · 35
  • 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=1
  • 100% F n=6
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

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