S12 12232 Chur – Sargans

View line S12

Chur 09:01 → Sargans 09:21 Daily 0 h 20 min · 5 stops Thurbo

✓ Today’s run finished

Today it reached Sargans at 09:21 −1 min

  1. Chur09:01
  2. Landquart09:09
  3. Maienfeld09:12
  4. Bad Ragaz09:15
  5. Sargans09:21

Next service: tomorrow 09:01 from Chur · Sat 7 Nov

Next departure 09:01 tomorrow · Chur
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 33 full · 0 partial · 1 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

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

  • Early 24% · 8
  • On time 76% · 25
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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 10
09:011 min early 1 min early
09:09≈ 1 min early ≈ on time
09:12≈ 1 min early ≈ on time
09:15≈ 1 min early ≈ on time
09:211 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 09:22−1 min—
Thu 5 NovSargans 09:19−1 min—
Wed 4 NovSargans 09:19−1 min—
Tue 3 NovSargans 09:19−1 min—
Mon 2 NovSargans 09:24+2 min+2 min
Sun 1 NovSargans 09:21−1 min—
Sat 31 OctSargans 09:21−1 min—
Fri 30 OctSargans 09:220 min—
Thu 29 OctSargans 09:22No data—
Wed 28 OctSargans 09:230 min—
Tue 27 OctSargans 09:21−1 min—
Mon 26 OctSargans 09:220 min—
Sun 25 OctSargans 09:21−1 min—
Sat 24 OctSargans 09:20−2 min—
Fri 23 OctSargans 09:210 min—
Thu 22 OctSargans 09:220 min—
Wed 21 OctSargans 09:21−1 min—
Tue 20 OctSargans 09:220 min—
Mon 19 OctSargans 09:220 min—
Sun 18 OctSargans 09:22−1 min—
Sat 17 OctSargans 09:21−1 min—
Fri 16 OctSargans 09:22−1 min—
Thu 15 OctSargans 09:220 min—
Wed 14 OctSargans 09:23+1 min—
Tue 13 OctSargans 09:21−1 min—
Mon 12 OctSargans 09:21−1 min—
Sun 11 OctSargans 09:21−1 min—
Sat 10 OctSargans 09:220 min—
Fri 9 OctSargans 09:21−1 min—
Thu 8 OctSargans 09:21−1 min—