S12 12219 Sargans – Chur

View line S12

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

✓ Today’s run finished

Today it reached Chur at 05:56 0 min

  1. Sargans05:36
  2. Bad Ragaz05:41
  3. Maienfeld05:43
  4. Landquart05:48
  5. Chur05:56

Next service: tomorrow 05:36 from Sargans · Sun 8 Nov

Next departure 05:36 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
97%
35/36 runs under 3 min
RT coverage: 36 full · 0 partial · 1 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

  • Thu 3 Sept Max en route +10 min · last fix heading to Chur +10 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 80% T n=5
  • 100% F n=6
  • 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, 36 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
05:36on time on time
05:41≈ on time ≈ on time
05:43≈ on time ≈ on time
05:48≈ on time ≈ +1 min
05: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
Sat 7 NovChur 05:570 min—
Fri 6 NovChur 05:570 min—
Thu 5 NovChur 05:58+1 min—
Wed 4 NovChur 05:570 min—
Tue 3 NovChur 05:570 min—
Mon 2 NovChur 05:580 min—
Sun 1 NovChur 05:570 min—
Sat 31 OctChur 05:570 min—
Fri 30 OctChur 05:570 min—
Thu 29 OctChur 05:570 min—
Wed 28 OctChur 05:58+1 min—
Tue 27 OctChur 05:58+1 min—
Mon 26 OctChur 05:560 min—
Sun 25 OctChur 05:58+1 min+1 min
Sat 24 OctChur 05:58+1 min+1 min
Fri 23 OctChur 05:570 min—
Thu 22 OctChur 05:570 min+2 min
Wed 21 OctChur 05:570 min—
Tue 20 OctChur 05:570 min—
Mon 19 OctChur 05:570 min—
Sun 18 OctChur 05:570 min—
Sat 17 OctChur 05:580 min—
Fri 16 OctChur 05:56−1 min—
Thu 15 OctChur 05:57No data—
Wed 14 OctChur 05:570 min—
Tue 13 OctChur 05:570 min—
Mon 12 OctChur 05:570 min—
Sun 11 OctChur 05:570 min—
Sat 10 OctChur 05:570 min—
Fri 9 OctChur 05:570 min—