R16 1460 Arosa – Chur

View line R16

Arosa 17:49 → Chur 18:51 Daily 1 h 02 min · 8 stops RhB

Running now · updated 18:19

Position estimated from the timetable

Between St. Peter-Molinis and Lüen-Castiel No data

Estimated arrival at Chur 18:51 · 25 km/h

  1. Arosa17:49
  2. Litzirüti17:58
  3. Langwies GR18:04
  4. St. Peter-Molinis18:16
  5. Lüen-Castiel18:24
  6. Chur Altstadt18:43
  7. Chur18:51
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 28 full · 1 partial · 1 no data
On-time · 90 days
100%
47/47 runs under 3 min
RT coverage: 46 full · 1 partial · 1 no data
Typical delay
−1min
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

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

  • Early 53% · 25
  • On time 47% · 22
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=6
  • 100% S n=7
  • 100% S n=7

Stops and timetable

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

Last 90 days, 47 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 10Today
17:49on time on timePassed
17:58≈ on time ≈ on timePassed
18:04 / 18:05≈ on time ≈ on timePassed
18:12≈ on time ≈ on timePassed
18:16≈ 1 min early ≈ on timePassed
18:24 / 18:28≈ 1 min early ≈ on timeNext
18:43 / 18:44≈ 1 min early ≈ on time
18:511 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 NovSt. Peter-Molinis 18:14Partial coverage0 min—
Wed 18 NovVevey 20:24+1 min+1 min
Tue 17 NovVevey 20:25−1 min—
Mon 16 NovVevey 20:240 min—
Sun 15 NovVevey 20:240 min—
Sat 14 NovVevey 20:240 min+1 min
Fri 13 NovVevey 20:240 min—
Thu 12 NovVevey 20:240 min—
Wed 11 NovVevey 20:240 min—
Tue 10 NovVevey 20:240 min—
Mon 9 NovVevey 20:24No data—
Sun 8 NovVevey 20:24−1 min+1 min
Sat 7 NovVevey 20:240 min—
Fri 6 NovVevey 20:240 min—
Thu 5 NovBlonay 20:040 min—
Wed 4 NovBlonay 20:04−2 min—
Tue 3 NovBlonay 20:04−2 min—
Mon 2 NovBlonay 20:040 min—
Sun 1 NovBlonay 20:040 min—
Sat 31 OctVevey 20:260 min+1 min
Fri 30 OctVevey 20:26−1 min—
Thu 29 OctBlonay 20:04−5 min+1 min
Wed 28 OctBlonay 20:06−3 min—
Tue 27 OctBlonay 20:090 min—
Mon 26 OctBlonay 20:06−3 min—
Sun 25 OctBlonay 20:04−4 min+2 min
Sat 24 OctVevey 20:28+3 min+3 min
Fri 23 OctVevey 20:25−1 min+2 min
Thu 22 OctBlonay 20:06−3 min—
Wed 21 OctBlonay 20:04−5 min—