S12 12288 Chur – Sargans

View line S12

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

It has not run yet today

Last recorded run: Friday 6 November −2 min

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

Next departure 23:01 today · Chur
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 6 no data
On-time · 90 days
98%
42/43 runs under 3 min
RT coverage: 43 full · 0 partial · 6 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

  • Thu 8 Oct Max en route +5 min · last fix heading to Sargans +5 min

Distribution · 90 days

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

  • Early 51% · 22
  • On time 47% · 20
  • 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=8
  • 100% W n=8
  • 80% T n=5
  • 100% F n=3
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

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