S12 12241 Sargans – Chur

View line S12

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

✓ Today’s run finished

Today, last fix heading to Chur at 11:27 No data

  1. Sargans11:06
  2. Bad Ragaz11:11
  3. Maienfeld11:13
  4. Landquart11:18
  5. Chur11:26

Next service: tomorrow 11:06 from Sargans · Fri 20 Nov

Next departure 11:06 tomorrow · Sargans
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 35 full · 0 partial · 11 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 35
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=7
  • 100% W n=7
  • 100% T n=1
  • 100% F n=5
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

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