RE8 1147 Chur – Thusis

View line RE8

Chur 14:28 → Thusis 14:58 Daily 0 h 30 min · 5 stops RhB

Running now · updated 14:43

Position estimated from the timetable

Between Domat/Ems and Bonaduz +1 min

Estimated arrival at Thusis 14:59 14:58 · 48 km/h

  1. Chur14:28
  2. Domat/Ems14:34
  3. Bonaduz14:43
  4. Rhäzüns14:45
  5. Thusis14:58

Today it is running worse than usual: typical arrival delay is 0 min; 100% of the last 30 runs arrived on time.

On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
100%
44/44 runs under 3 min
RT coverage: 43 full · 1 partial · 0 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 Thusis, 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

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

  • Early 5% · 2
  • On time 95% · 42
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 44 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
14:28on time on timePassed
14:34≈ on time ≈ on timePassed
14:43≈ on time ≈ on timeNext
14:45≈ on time ≈ on time
14:58on 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
Wed 18 NovBonaduz 14:39Partial coverage+1 min+1 min
Tue 17 NovSolothurn 15:24−1 min—
Mon 16 NovSolothurn 15:240 min—
Sun 15 NovThusis 14:58−1 min—
Sat 14 NovThusis 14:58−1 min—
Fri 13 NovSolothurn 15:240 min—
Thu 12 NovSolothurn 15:240 min—
Wed 11 NovSolothurn 15:240 min—
Tue 10 NovSolothurn 15:240 min—
Mon 9 NovSolothurn 15:240 min—
Sun 8 NovThusis 14:59−1 min—
Sat 7 NovThusis 14:590 min—
Fri 6 NovSolothurn 15:240 min—
Thu 5 NovSolothurn 15:240 min—
Wed 4 NovSolothurn 15:240 min—
Tue 3 NovSolothurn 15:240 min—
Mon 2 NovSolothurn 15:240 min—
Sun 1 NovThusis 14:580 min—
Sat 31 OctThusis 14:590 min—
Fri 30 OctSolothurn 15:260 min+1 min
Thu 29 OctSolothurn 15:260 min—
Wed 28 OctSolothurn 15:260 min+1 min
Tue 27 OctSolothurn 15:26−1 min—
Mon 26 OctSolothurn 15:260 min—
Sun 25 OctThusis 14:590 min—
Sat 24 OctThusis 14:58−1 min—
Fri 23 OctSolothurn 15:250 min—
Thu 22 OctSolothurn 15:260 min—
Wed 21 OctSolothurn 15:260 min—
Tue 20 OctSolothurn 15:260 min—