S12 12239 Sargans – Chur

View line S12

Sargans 10:36 → Chur 10:56 Daily 0 h 20 min · 5 stops Thurbo

It has not run yet today

Last recorded run: Wednesday 11 November 0 min

Next service: today 10:36 from Sargans · Thu 12 Nov

Next departure 10:36 today · Sargans
On-time · 30 days
93%
25/27 runs under 3 min
RT coverage: 27 full · 0 partial · 1 no data
On-time · 90 days
93%
38/41 runs under 3 min
RT coverage: 41 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Chur, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 6 Oct Max en route +4 min · last fix heading to Chur +4 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Chur +4 min
  • Mon 2 Nov Max en route +4 min · last fix heading to Chur +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 38
  • 3–10 min 7% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 83% T n=6
  • 100% W n=6
  • 100% T n=4
  • 100% F n=5
  • 100% S n=6
  • 88% S n=8

Stops and timetable

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

Last 90 days, 41 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
10:36on time +1 min
10:41≈ on time ≈ +2 min
10:43≈ on time ≈ +2 min
10:48≈ on time ≈ +2 min
10:56on time +3 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
Wed 11 NovChur 10:570 min—
Tue 10 NovChur 10:570 min—
Mon 9 NovChur 10:570 min—
Sun 8 NovChur 10:570 min—
Sat 7 NovChur 10:540 min—
Fri 6 NovChur 10:570 min—
Thu 5 NovChur 10:570 min—
Wed 4 NovChur 10:580 min—
Tue 3 NovChur 10:570 min—
Mon 2 NovChur 10:57+4 min+4 min
Sun 1 NovChur 10:570 min—
Sat 31 OctChur 10:570 min—
Fri 30 OctChur 10:570 min—
Thu 29 OctChur 10:57No data—
Wed 28 OctChur 10:570 min—
Tue 27 OctChur 10:570 min—
Mon 26 OctSargans 11:010 min—
Sun 25 OctChur 10:570 min—
Sat 24 OctChur 10:570 min—
Thu 22 OctChur 10:580 min—
Wed 21 OctChur 10:570 min—
Tue 20 OctChur 10:580 min—
Mon 19 OctChur 10:58+1 min+1 min
Sun 18 OctChur 11:02+4 min+4 min
Sat 17 OctChur 10:570 min—
Fri 16 OctChur 10:59+1 min+1 min
Thu 15 OctChur 11:00+3 min+3 min
Wed 14 OctChur 10:570 min—
Tue 13 OctChur 10:580 min—
Mon 12 OctChur 10:57+1 min—