S12 12243 Sargans → Chur

View line S12

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

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

✓ Today’s run finished

Today it reached Chur at 11:56 0 min

  1. Sargans11:36
  2. Bad Ragaz11:41
  3. Maienfeld11:43
  4. Landquart11:48
  5. Chur11:56

Next service: tomorrow 11:36 from Sargans · Mon 23 Nov

Next departure 11:36 tomorrow · Sargans
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
93%
38/41 runs under 3 min
RT coverage: 41 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: 0 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

  • Wed 4 Nov Max en route +5 min · last fix heading to Chur +5 min
  • Tue 17 Nov Max en route +5 min · last fix heading to Chur +5 min
  • Fri 16 Oct Max en route +4 min · last fix heading to Chur +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 88% T n=8
  • 86% W n=7
  • 100% T n=1
  • 83% F n=6
  • 100% S n=7
  • 100% S n=9

Stops and timetable

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

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