S12 12287 Sargans – Chur

View line S12

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 22:36 from Sargans · Fri 6 Nov

Next departure 22:36 today · Sargans
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
95%
38/40 runs under 3 min
RT coverage: 40 full · 0 partial · 0 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 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

  • Fri 23 Oct Max en route +3 min · last fix heading to Chur +3 min
  • Mon 19 Oct Max en route +3 min · last fix heading to Chur +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 38
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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