S12 12290 Chur – Sargans

View line S12

Chur 23:31 → Sargans 23:51 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 23:31 from Chur · Sat 7 Nov

Next departure 23:31 today · Chur
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 26 full · 0 partial · 3 no data
On-time · 90 days
97%
32/33 runs under 3 min
RT coverage: 33 full · 0 partial · 3 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

Worst days

  • Fri 23 Oct Max en route +3 min · last fix heading to Sargans +3 min

Distribution · 90 days

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

  • Early 30% · 10
  • On time 67% · 22
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 33 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:31on time on time
23:39≈ on time ≈ on time
23:42≈ on time ≈ +1 min
23:45≈ on time ≈ +1 min
23: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
Fri 6 NovSargans 23:49−1 min—
Thu 5 NovSargans 23:520 min—
Wed 4 NovSargans 23:520 min—
Tue 3 NovSargans 23:53+1 min+1 min
Mon 2 NovSargans 23:520 min—
Sun 1 NovSargans 23:49−1 min—
Sat 31 OctSargans 23:51−1 min—
Fri 30 OctSargans 23:54+2 min+3 min
Thu 29 OctSargans 23:520 min—
Wed 28 OctSargans 23:51−1 min—
Tue 27 OctSargans 23:51−1 min—
Mon 26 OctSargans 23:51−2 min—
Sun 25 OctSargans 23:510 min—
Sat 24 OctSargans 23:50−2 min—
Fri 23 OctSargans 23:55+3 min+3 min
Thu 22 OctSargans 23:53+1 min+1 min
Wed 21 OctSargans 23:520 min—
Tue 20 OctSargans 23:520 min—
Mon 19 OctSargans 23:520 min—
Sun 18 OctSargans 23:520 min—
Sat 17 OctSargans 23:51−1 min—
Fri 16 OctSargans 23:52No data—
Thu 15 OctSargans 23:52No data—
Wed 14 OctSargans 23:520 min—
Tue 13 OctSargans 23:52No data—
Mon 12 OctSargans 23:510 min—
Sun 11 OctSargans 23:51−1 min—
Sat 10 OctSargans 23:51−1 min—
Fri 9 OctSargans 23:52−1 min—
Thu 8 OctSargans 23:53+1 min—