S12 12242 Chur → Sargans

View line S12

Chur 11:31 → Sargans 11:51 Daily 0 h 20 min · 5 stops Thurbo

S12 12242 Chur–Sargans: final delay under 3 min on 22 of its 22 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 12:01 (GMT+1).

✓ Today’s run finished

Today it reached Sargans at 11:51 0 min

  1. Chur11:31
  2. Landquart11:39
  3. Maienfeld11:42
  4. Bad Ragaz11:45
  5. Sargans11:51

Next service: tomorrow 11:31 from Chur · Mon 23 Nov

Next departure 11:31 tomorrow · Chur
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
97%
37/38 runs under 3 min
RT coverage: 38 full · 0 partial · 12 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 Sargans, 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 8 Oct Max en route +5 min · last fix heading to Sargans +5 min

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 97% · 37
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=7
  • 100% W n=7
  • 0% T n=1
  • 100% F n=7
  • 100% S n=7
  • 100% S n=8

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
11:31on time on time
11:39≈ on time ≈ +1 min
11:42≈ on time ≈ +1 min
11:45≈ on time ≈ +1 min
11:51on 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
Sun 22 NovSargans 11:520 min—
Sat 21 NovSargans 11:49−1 min—
Fri 20 NovSargans 11:520 min—
Thu 19 NovSargans 11:52No data—
Wed 18 NovSargans 11:520 min—
Tue 17 NovSargans 11:54+2 min+2 min
Mon 16 NovSargans 11:52No data—
Sun 15 NovSargans 11:53+1 min—
Sat 14 NovSargans 11:49−1 min—
Fri 13 NovSargans 11:53+1 min—
Thu 12 NovSargans 11:52No data—
Wed 11 NovSargans 11:520 min—
Tue 10 NovSargans 11:49−1 min—
Mon 9 NovSargans 11:52No data—
Sun 8 NovSargans 11:520 min—
Sat 7 NovSargans 11:520 min—
Fri 6 NovSargans 11:54+1 min+1 min
Thu 5 NovSargans 11:52No data—
Wed 4 NovSargans 11:520 min—
Tue 3 NovSargans 11:520 min—
Mon 2 NovSargans 11:52No data—
Sun 1 NovSargans 11:51−1 min—
Sat 31 OctSargans 11:52+1 min—
Fri 30 OctSargans 11:520 min—
Thu 29 OctSargans 11:52No data—
Wed 28 OctSargans 11:53+1 min—
Tue 27 OctSargans 11:520 min—
Mon 26 OctSargans 11:53No data—
Sun 25 OctSargans 11:520 min—
Sat 24 OctSargans 11:53+1 min+1 min