R16 1409 Chur – Arosa

View line R16

Chur 04:59 → Arosa 05:57 Mon, Tue, Wed, Thu, Fri, Sat 0 h 58 min · 8 stops RhB

It has not run yet today

Last recorded run: Thursday 19 November −1 min

Next service: today 04:59 from Chur · Fri 20 Nov

Next departure 04:59 today · Chur
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 0 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 34 full · 0 partial · 1 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Arosa, 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 7 Oct Max en route +3 min · last fix heading to Arosa +3 min

Distribution · 90 days

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

  • Early 59% · 20
  • On time 38% · 13
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 83% W n=6
  • 100% T n=6
  • 100% F n=5
  • 100% S n=6
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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
04:59on time on time
05:01≈ on time ≈ on time
05:19 / 05:20≈ on time ≈ on time
05:28≈ 1 min early ≈ on time
05:32≈ 1 min early ≈ on time
05:40≈ 1 min early ≈ on time
05:46≈ 1 min early ≈ on time
05:571 min early 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
Thu 19 NovArosa 05:54−1 min—
Wed 18 NovArosa 05:57−2 min—
Tue 17 NovArosa 05:57−1 min—
Mon 16 NovArosa 05:57−1 min—
Sat 14 NovArosa 05:580 min—
Fri 13 NovArosa 05:580 min—
Thu 12 NovArosa 05:560 min—
Wed 11 NovArosa 05:57−1 min—
Tue 10 NovArosa 05:580 min—
Mon 9 NovArosa 05:54−1 min—
Sat 7 NovArosa 05:57−1 min—
Fri 6 NovArosa 05:57−1 min—
Thu 5 NovArosa 05:54−1 min—
Wed 4 NovArosa 05:57−2 min—
Tue 3 NovArosa 05:57−1 min—
Mon 2 NovArosa 05:57−1 min—
Sat 31 OctArosa 05:56−2 min—
Fri 30 OctArosa 05:56−2 min—
Thu 29 OctArosa 05:57−1 min—
Wed 28 OctArosa 05:57−2 min—
Tue 27 OctArosa 05:57−1 min—
Mon 26 OctArosa 05:57−1 min—
Sat 24 OctArosa 05:57−1 min—
Sat 17 OctArosa 05:57−2 min—
Fri 16 OctArosa 05:57−1 min—
Thu 15 OctArosa 06:00+1 min+1 min
Wed 14 OctArosa 05:56−2 min—
Tue 13 OctArosa 05:58No data—
Mon 12 OctArosa 05:56−2 min—
Sat 10 OctArosa 05:57−2 min—