S12 12284 Chur – Sargans

View line S12

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

✓ Today’s run finished

Today it reached Sargans at 22:21 −2 min

  1. Chur22:01
  2. Landquart22:09
  3. Maienfeld22:12
  4. Bad Ragaz22:15
  5. Sargans22:21

Next service: tomorrow 22:01 from Chur · Sat 21 Nov

Next departure 22: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
98%
46/47 runs under 3 min
RT coverage: 47 full · 0 partial · 2 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: −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

Worst days

  • Sat 10 Oct Max en route +4 min · last fix heading to Sargans +4 min

Distribution · 90 days

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

  • Early 57% · 27
  • On time 40% · 19
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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