S12 12280 Chur – Sargans

View line S12

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

It has not run yet today

Last recorded run: Friday 6 November −1 min

Next service: today 21:01 from Chur · Sat 7 Nov

Next departure 21:01 today · Chur
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 2 no data
On-time · 90 days
97%
38/39 runs under 3 min
RT coverage: 39 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

Worst days

  • Sat 22 Aug Max en route +6 min · last fix heading to Olten +6 min

Distribution · 90 days

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

  • Early 13% · 5
  • On time 85% · 33
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 39 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
21:011 min early on time
21:09≈ on time ≈ on time
21:12≈ on time ≈ on time
21:15≈ on time ≈ on time
21:21on 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
Fri 6 NovSargans 21:19−1 min—
Thu 5 NovSargans 21:18−1 min—
Wed 4 NovSargans 21:19−1 min—
Tue 3 NovSargans 21:220 min—
Mon 2 NovSargans 21:22−1 min—
Sun 1 NovSargans 21:19−2 min—
Sat 31 OctSargans 21:21−1 min—
Fri 30 OctSargans 21:23+1 min+1 min
Thu 29 OctSargans 21:23+1 min—
Wed 28 OctSargans 21:220 min—
Tue 27 OctSargans 21:220 min—
Mon 26 OctSargans 21:220 min—
Sun 25 OctSargans 21:210 min—
Sat 24 OctSargans 21:23+1 min+1 min
Fri 23 OctSargans 21:220 min—
Thu 22 OctSargans 21:220 min—
Wed 21 OctSargans 21:220 min—
Tue 20 OctSargans 21:21−1 min—
Mon 19 OctSargans 21:210 min—
Sun 18 OctSargans 21:220 min—
Sat 17 OctSargans 21:21−1 min—
Fri 16 OctSargans 21:22No data—
Thu 15 OctSargans 21:22No data—
Wed 14 OctSargans 21:22−1 min—
Tue 13 OctSargans 21:220 min—
Mon 12 OctSargans 21:220 min—
Sun 11 OctSargans 21:21−1 min—
Sat 10 OctSargans 21:22−1 min—
Fri 9 OctSargans 21:22−1 min—
Thu 8 OctSargans 21:24+2 min+2 min