S2 1577 Chur – Rhäzüns

View line S2

Chur 06:08 → Rhäzüns 06:28 Sun 0 h 20 min · 8 stops RhB

It does not run today

Last recorded run: Sunday 8 November 0 min

Next service: Sunday 06:08 from Chur · Sun 15 Nov

Next departure 06:08 Sunday · Chur
On-time · 30 days
75%
3/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
78%
7/9 runs under 3 min
RT coverage: 9 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Rhäzüns, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 6 Sept Max en route +4 min · last fix heading to Bonaduz +3 min
  • Sun 25 Oct Max en route +3 min · last fix heading to Rhäzüns +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 7
  • 3–10 min 22% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • — S n=0
  • 78% S n=9

Stops and timetable

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

Last 90 days, 9 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:08on time on time
06:10≈ on time ≈ on time
06:13≈ on time ≈ +1 min
06:16≈ on time ≈ +1 min
06:18≈ on time ≈ +2 min
06:21≈ on time ≈ +2 min
06:26≈ on time ≈ +3 min
06:28on time +3 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 8 NovRhäzüns 06:290 min—
Sun 1 NovRhäzüns 06:30+1 min—
Sun 25 OctRhäzüns 06:32+3 min+3 min
Sun 18 OctRhäzüns 06:290 min—
Sun 11 OctRhäzüns 06:29No data—
Mon 5 OctRhäzüns 06:30No data—
Sun 4 OctRhäzüns 06:280 min—
Sat 3 OctRhäzüns 06:28No data—
Mon 28 SeptRhäzüns 06:27No data—
Sat 26 SeptRhäzüns 06:27No data—
Fri 25 SeptRhäzüns 06:27No data—
Sun 20 SeptRhäzüns 06:27−1 min—
Mon 14 SeptRhäzüns 06:27No data—
Sat 12 SeptRhäzüns 06:27No data—
Mon 7 SeptRhäzüns 06:27No data—
Sun 6 SeptBonaduz 06:27+3 min+4 min
Sat 5 SeptRhäzüns 06:27No data—
Sat 29 AugRhäzüns 06:27No data—
Sun 23 AugRhäzüns 06:270 min—
Sun 16 AugRhäzüns 06:270 min—