S12 12222 Chur – Sargans

View line S12

Chur 06:31 → Sargans 06:51 Mon, Tue, Wed, Thu, Fri, Sat 0 h 20 min · 5 stops Thurbo

✓ Today’s run finished

Today it reached Sargans at 06:51 −1 min

  1. Chur06:31
  2. Landquart06:39
  3. Maienfeld06:42
  4. Bad Ragaz06:45
  5. Sargans06:51

Next service: Monday 06:31 from Chur · Mon 9 Nov

Next departure 06:31 Monday · Chur
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 0 no data
On-time · 90 days
100%
31/31 runs under 3 min
RT coverage: 31 full · 0 partial · 0 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: +1 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

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

  • Early 6% · 2
  • On time 94% · 29
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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:31on time on time
06:39≈ on time ≈ on time
06:42≈ on time ≈ on time
06:45≈ on time ≈ on time
06:51on time +1 min

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:49−1 min—
Fri 6 NovSargans 06:53+1 min+1 min
Thu 5 NovSargans 06:520 min—
Wed 4 NovSargans 06:520 min—
Tue 3 NovSargans 06:49−1 min—
Mon 2 NovSargans 06:54+1 min+1 min
Sat 31 OctSargans 06:520 min—
Fri 30 OctSargans 06:520 min—
Thu 29 OctSargans 06:51−1 min—
Wed 28 OctSargans 06:530 min—
Tue 27 OctSargans 06:53+1 min+1 min
Mon 26 OctSargans 06:51−1 min—
Sat 24 OctSargans 06:51−1 min—
Fri 23 OctSargans 06:520 min—
Thu 22 OctSargans 06:520 min—
Wed 21 OctSargans 06:53+1 min—
Tue 20 OctSargans 06:52−1 min—
Mon 19 OctSargans 06:51−1 min—
Sat 17 OctSargans 06:53+1 min—
Fri 16 OctSargans 06:52+1 min—
Thu 15 OctSargans 06:520 min—
Wed 14 OctSargans 06:520 min—
Tue 13 OctSargans 06:510 min—
Mon 12 OctSargans 06:520 min—
Sat 10 OctSargans 06:530 min—
Fri 9 OctSargans 06:51−1 min—
Thu 8 OctSargans 06:520 min—
Wed 7 OctSargans 06:51−1 min—
Tue 6 OctSargans 06:51−1 min—
Mon 5 OctSargans 06:53+1 min—