S12 12235 Sargans – Chur

View line S12

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

✓ Today’s run finished

Today it reached Chur at 18:56 0 min

  1. Sargans18:36
  2. Bad Ragaz18:41
  3. Maienfeld18:43
  4. Landquart18:48
  5. Chur18:56

Next service: tomorrow 18:36 from Sargans · Fri 6 Nov

Next departure 18:36 tomorrow · Sargans
On-time · 30 days
90%
26/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
88%
28/32 runs under 3 min
RT coverage: 32 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 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 16 Oct Max en route +9 min · last fix heading to Chur +9 min
  • Wed 14 Oct Max en route +6 min · last fix heading to Chur +6 min
  • Mon 5 Oct Max en route +4 min · last fix heading to Chur +4 min
  • Thu 8 Oct Max en route +4 min · last fix heading to Chur +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 28
  • 3–10 min 13% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 80% W n=5
  • 75% T n=4
  • 75% F n=4
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

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