S12 12220 Chur – Sargans

View line S12

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

✓ Today’s run finished

Today it reached Sargans at 06:21 −2 min

  1. Chur06:01
  2. Landquart06:09
  3. Maienfeld06:12
  4. Bad Ragaz06:15
  5. Sargans06:21

Next service: tomorrow 06:01 from Chur · Sun 8 Nov

Next departure 06:01 tomorrow · Chur
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
38/38 runs under 3 min
RT coverage: 38 full · 0 partial · 0 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 29% · 11
  • On time 71% · 27
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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