S12 12228 Chur – Sargans

View line S12

Chur 08:01 → Sargans 08:21 Daily 0 h 20 min · 5 stops Thurbo

✓ Today’s run finished

Today it reached Sargans at 08:21 0 min

  1. Chur08:01
  2. Landquart08:09
  3. Maienfeld08:12
  4. Bad Ragaz08:15
  5. Sargans08:21

Next service: tomorrow 08:01 from Chur · Sat 7 Nov

Next departure 08:01 tomorrow · Chur
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%
34/34 runs under 3 min
RT coverage: 34 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Sargans, 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

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

  • Early 29% · 10
  • On time 71% · 24
  • 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=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 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, 34 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
08:011 min early 1 min early
08:09≈ 1 min early ≈ on time
08:12≈ 1 min early ≈ on time
08:15≈ 1 min early ≈ on time
08:21on time on time

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 6 NovSargans 08:220 min—
Thu 5 NovSargans 08:19−1 min—
Wed 4 NovSargans 08:19−1 min—
Tue 3 NovSargans 08:220 min—
Mon 2 NovSargans 08:230 min—
Sun 1 NovSargans 08:210 min—
Sat 31 OctSargans 08:21−1 min—
Fri 30 OctSargans 08:220 min—
Thu 29 OctSargans 08:24+2 min+2 min
Wed 28 OctSargans 08:220 min—
Tue 27 OctSargans 08:220 min—
Mon 26 OctSargans 08:21−2 min—
Sun 25 OctSargans 08:21−1 min—
Sat 24 OctSargans 08:20−1 min—
Fri 23 OctSargans 08:210 min—
Thu 22 OctSargans 08:21−1 min—
Wed 21 OctSargans 08:220 min—
Tue 20 OctSargans 08:23+1 min—
Mon 19 OctSargans 08:20−2 min—
Sun 18 OctSargans 08:21−1 min—
Sat 17 OctSargans 08:21−1 min—
Fri 16 OctSargans 08:20−1 min—
Thu 15 OctSargans 08:21−1 min—
Wed 14 OctSargans 08:220 min—
Tue 13 OctSargans 08:220 min—
Mon 12 OctSargans 08:21−1 min—
Sun 11 OctSargans 08:220 min—
Sat 10 OctSargans 08:220 min—
Fri 9 OctSargans 08:21−1 min—
Thu 8 OctSargans 08:220 min—