R16 1481 Chur – Arosa

View line R16

Chur 23:00 → Arosa 23:58 Mon, Thu, Fri, Sat, Sun 0 h 58 min · 8 stops RhB

It does not run today

Last recorded run: Sunday 8 November −2 min

Next service: tomorrow 23:00 from Chur · Fri 13 Nov

Next departure 23:00 tomorrow · Chur
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −2 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: −1 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

  • Sat 29 Aug Max en route +5 min · last fix heading to Arosa +5 min

Distribution · 90 days

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

  • Early 52% · 15
  • On time 45% · 13
  • 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=1
  • — W n=0
  • — T n=0
  • 100% F n=9
  • 92% S n=12
  • 100% S n=6

Stops and timetable

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

Last 90 days, 29 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
23:00on time +1 min
23:02≈ on time ≈ on time
23:19 / 23:20≈ on time ≈ on time
23:28 / 23:29≈ on time ≈ on time
23:32≈ 1 min early ≈ on time
23:40 / 23:41≈ 1 min early ≈ on time
23:46 / 23:47≈ 1 min early ≈ on time
23:581 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
Sun 8 NovArosa 23:58−2 min—
Sat 7 NovArosa 23:57−1 min—
Fri 6 NovArosa 23:57−2 min—
Sun 1 NovArosa 23:58−2 min—
Sat 31 OctArosa 23:58−1 min—
Fri 30 OctArosa 23:57−2 min—
Sun 25 OctArosa 23:58−1 min—
Sat 24 OctArosa 23:58−1 min—
Sat 17 OctArosa 23:580 min—
Fri 16 OctArosa 23:57−2 min—
Sun 11 OctArosa 23:58−1 min—
Sat 10 OctArosa 00:01+2 min+2 min
Fri 9 OctArosa 00:000 min—
Sun 4 OctArosa 23:58−1 min—
Sat 3 OctArosa 23:58−2 min—
Tue 29 SeptArosa 23:570 min—
Mon 28 SeptArosa 23:580 min—
Sun 27 SeptArosa 23:570 min—
Tue 22 SeptArosa 23:57No data—
Sat 19 SeptArosa 23:58+3 min+3 min
Fri 18 SeptArosa 23:57−2 min—
Sat 12 SeptArosa 23:570 min—
Fri 11 SeptArosa 23:57−1 min+1 min
Sat 5 SeptArosa 23:570 min+1 min
Fri 4 SeptArosa 23:57−2 min—
Sat 29 AugArosa 23:57+5 min+5 min
Fri 28 AugArosa 23:57−1 min—
Sat 22 AugArosa 23:57−2 min—
Fri 21 AugArosa 23:570 min—
Sat 15 AugArosa 23:57+1 min+1 min