R16 1412 Arosa – Chur

View line R16

Arosa 06:02 → Chur 07:00 Mon, Tue, Wed, Thu, Fri, Sat 0 h 58 min · 8 stops RhB

✓ Today’s run finished

Today it reached Chur at 07:00 0 min

  1. Arosa06:02
  2. Litzirüti06:12
  3. Langwies GR06:18
  4. St. Peter-Molinis06:30
  5. Lüen-Castiel06:38
  6. Chur Altstadt06:54
  7. Chur07:00

Next service: tomorrow 06:02 from Arosa · Sat 7 Nov

Next departure 06:02 tomorrow · Arosa
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 1 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

Distribution · 90 days

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

  • Early 17% · 5
  • On time 83% · 25
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=4
  • 100% T n=4
  • 100% F n=6
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 30 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:02on time on time
06:12≈ on time ≈ on time
06:18≈ on time ≈ on time
06:26≈ on time ≈ on time
06:30≈ on time ≈ on time
06:38 / 06:39≈ on time ≈ on time
06:54≈ on time ≈ on time
07:00on time 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
Fri 6 NovChur 07:020 min—
Thu 5 NovChur 06:590 min—
Wed 4 NovChur 06:590 min—
Tue 3 NovChur 06:590 min—
Mon 2 NovChur 06:590 min—
Sat 31 OctChur 07:00−1 min—
Fri 30 OctChur 07:010 min—
Thu 29 OctChur 07:010 min—
Wed 28 OctChur 07:010 min—
Tue 27 OctChur 07:010 min—
Mon 26 OctChur 07:020 min—
Sat 24 OctChur 07:010 min—
Sat 17 OctChur 07:01−1 min—
Fri 16 OctChur 07:010 min—
Thu 15 OctChur 07:010 min—
Wed 14 OctChur 07:010 min—
Tue 13 OctChur 07:02No data—
Mon 12 OctChur 07:010 min—
Sat 10 OctChur 07:010 min—
Fri 9 OctChur 07:010 min—
Thu 8 OctChur 07:010 min—
Wed 7 OctChur 07:02+1 min—
Tue 6 OctChur 07:010 min—
Mon 5 OctChur 07:020 min—
Sun 13 SeptChur 01:00−2 min+3 min
Sun 6 SeptChur 01:00−5 min+2 min
Fri 4 SeptChur 01:00−4 min+2 min
Sun 30 AugChur 01:00−3 min+12 min
Sat 29 AugChur 01:00+3 min+4 min
Fri 28 AugChur 01:00−4 min+5 min