RE8 1162 Thusis – Chur

View line RE8

Thusis 19:02 → Chur 19:31 Daily 0 h 29 min · 5 stops RhB

It has not run yet today

Last recorded run: Wednesday 11 November +1 min

Next service: today 19:02 from Thusis · Thu 12 Nov

Next departure 19:02 today · Thusis
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
95%
37/39 runs under 3 min
RT coverage: 39 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Tue 13 Oct Max en route +11 min · last fix heading to Chur +11 min
  • Sat 17 Oct Max en route +6 min · last fix heading to Chur +5 min

Distribution · 90 days

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

  • Early 10% · 4
  • On time 85% · 33
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 83% T n=6
  • 100% W n=6
  • 100% T n=5
  • 100% F n=5
  • 80% 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, 39 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
19:02on time on time
19:13 / 19:14≈ on time ≈ +1 min
19:16 / 19:17≈ on time ≈ +1 min
19:25≈ on time ≈ +2 min
19:31on time +2 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
Wed 11 NovChur 19:33+1 min—
Tue 10 NovChur 19:320 min—
Mon 9 NovChur 19:33+1 min—
Sun 8 NovChur 19:320 min—
Sat 7 NovChur 19:29−1 min—
Fri 6 NovChur 19:34+2 min+2 min
Thu 5 NovChur 19:29−1 min—
Wed 4 NovChur 19:320 min—
Tue 3 NovChur 19:33+1 min—
Mon 2 NovChur 19:320 min—
Sun 1 NovChur 19:320 min—
Sat 31 OctChur 19:33+1 min—
Fri 30 OctChur 19:320 min—
Thu 29 OctChur 19:320 min—
Wed 28 OctChur 19:33+1 min—
Tue 27 OctChur 19:34+2 min+2 min
Mon 26 OctChur 19:320 min—
Sun 25 OctChur 19:33+2 min+2 min
Sat 24 OctChur 19:31−1 min—
Fri 23 OctChur 19:320 min—
Thu 22 OctChur 19:320 min—
Wed 21 OctChur 19:34+2 min+2 min
Tue 20 OctChur 19:320 min—
Mon 19 OctChur 19:320 min—
Sun 18 OctChur 19:33+1 min+1 min
Sat 17 OctChur 19:37+5 min+6 min
Fri 16 OctChur 19:330 min—
Thu 15 OctChur 19:33+1 min—
Wed 14 OctChur 19:31−1 min+3 min
Tue 13 OctChur 19:43+11 min+11 min