R16 1452 Arosa – Chur

View line R16

Arosa 15:49 → Chur 16:51 Daily 1 h 02 min · 8 stops RhB

✓ Today’s run finished

Today it reached Chur at 16:51 0 min

  1. Arosa15:49
  2. Litzirüti15:58
  3. Langwies GR16:04
  4. St. Peter-Molinis16:16
  5. Lüen-Castiel16:24
  6. Chur Altstadt16:43
  7. Chur16:51

Next service: tomorrow 15:49 from Arosa · Sun 15 Nov

Next departure 15:49 tomorrow · Arosa
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
98%
40/41 runs under 3 min
RT coverage: 41 full · 0 partial · 1 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: +1 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

  • Thu 8 Oct Max en route +4 min · last fix heading to Vevey +4 min

Distribution · 90 days

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

  • Early 22% · 9
  • On time 76% · 31
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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
15:49on time on time
15:58≈ on time ≈ on time
16:04 / 16:05≈ on time ≈ on time
16:12≈ on time ≈ on time
16:16≈ on time ≈ +1 min
16:24 / 16:28≈ on time ≈ +1 min
16:43 / 16:44≈ on time ≈ +1 min
16:51on 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
Sat 14 NovChur 16:490 min—
Fri 13 NovVevey 18:24No data—
Thu 12 NovVevey 18:240 min—
Wed 11 NovVevey 18:240 min—
Tue 10 NovVevey 18:24−2 min—
Mon 9 NovVevey 18:240 min—
Sun 8 NovVevey 18:240 min+2 min
Sat 7 NovVevey 18:240 min—
Fri 6 NovVevey 18:240 min—
Thu 5 NovVevey 18:240 min—
Wed 4 NovVevey 18:240 min—
Tue 3 NovVevey 18:240 min—
Mon 2 NovVevey 18:24+1 min—
Sun 1 NovVevey 18:24−1 min—
Sat 31 OctVevey 18:26+1 min+2 min
Fri 30 OctVevey 18:26−1 min—
Thu 29 OctVevey 18:26−1 min—
Wed 28 OctVevey 18:260 min—
Tue 27 OctVevey 18:25−2 min—
Mon 26 OctVevey 18:28+1 min+3 min
Sun 25 OctVevey 18:25−1 min+1 min
Sat 24 OctVevey 18:260 min+1 min
Fri 23 OctVevey 18:28+2 min+2 min
Thu 22 OctVevey 18:27+1 min+3 min
Wed 21 OctVevey 18:25−1 min+2 min
Tue 20 OctVevey 18:25−1 min—
Mon 19 OctVevey 18:240 min—
Sun 18 OctVevey 18:24−2 min+2 min
Sat 17 OctVevey 18:24−2 min+1 min
Fri 16 OctVevey 18:25+1 min+2 min