S12 12285 Sargans – Chur

View line S12

Sargans 22:06 → Chur 22:26 Daily 0 h 20 min · 5 stops Thurbo

✓ Today’s run finished

Today it reached Chur at 22:26 0 min

  1. Sargans22:06
  2. Bad Ragaz22:11
  3. Maienfeld22:13
  4. Landquart22:18
  5. Chur22:26

Next service: tomorrow 22:06 from Sargans · Sat 21 Nov

Next departure 22:06 tomorrow · Sargans
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%
52/53 runs under 3 min
RT coverage: 53 full · 0 partial · 2 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: 0 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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 52
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 53 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:06on time on time
22:11≈ on time ≈ on time
22:13≈ on time ≈ on time
22:18≈ on time ≈ +1 min
22:26on 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 20 NovChur 22:270 min—
Thu 19 NovChur 22:270 min—
Wed 18 NovChur 22:270 min—
Tue 17 NovChur 22:240 min—
Mon 16 NovChur 22:270 min—
Sun 15 NovChur 22:270 min—
Sat 14 NovChur 22:240 min—
Fri 13 NovChur 22:270 min—
Thu 12 NovChur 22:28No data—
Wed 11 NovChur 22:270 min—
Tue 10 NovChur 22:240 min—
Mon 9 NovChur 22:240 min—
Sun 8 NovChur 22:270 min—
Sat 7 NovChur 22:240 min—
Fri 6 NovChur 22:280 min—
Thu 5 NovChur 22:270 min—
Wed 4 NovChur 22:270 min—
Tue 3 NovChur 22:27−1 min—
Mon 2 NovChur 22:270 min—
Sun 1 NovChur 22:280 min—
Sat 31 OctChur 22:270 min—
Fri 30 OctChur 22:270 min—
Thu 29 OctChur 22:270 min—
Wed 28 OctChur 22:28+1 min+1 min
Tue 27 OctChur 22:270 min—
Mon 26 OctChur 22:280 min—
Sun 25 OctChur 22:270 min—
Sat 24 OctChur 22:28+1 min+1 min
Fri 23 OctChur 22:270 min—
Thu 22 OctChur 22:270 min—