S12 12223 Sargans – Chur

View line S12

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

✓ Today’s run finished

Today it reached Chur at 06:56 0 min

  1. Sargans06:36
  2. Bad Ragaz06:41
  3. Maienfeld06:43
  4. Landquart06:48
  5. Chur06:56

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

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

Distribution · 90 days

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

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

On-time by weekday

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