RE5 1767 Chur – Ilanz

View line RE5

Chur 19:25 → Ilanz 19:58 Daily 0 h 33 min · 4 stops RhB

It has not run yet today

Last recorded run: Saturday 7 November −2 min

Next service: today 19:25 from Chur · Sun 8 Nov

Next departure 19:25 today · Chur
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
95%
54/57 runs under 3 min
RT coverage: 57 full · 0 partial · 5 no data
Typical delay
−2min
Median at arrival, 90 days
30 days: −2 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: −1 min

Last 30 days

Arrival delay at Ilanz, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 14 Aug Max en route +6 min · last fix heading to Zürich HB +6 min
  • Sat 26 Sept Max en route +4 min · last fix heading to Zürich HB +4 min
  • Tue 1 Sept Max en route +3 min · last fix heading to Zürich HB +3 min

Distribution · 90 days

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

  • Early 54% · 31
  • On time 40% · 23
  • 3–10 min 5% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 89% T n=9
  • 100% W n=9
  • 100% T n=6
  • 90% F n=10
  • 86% S n=7
  • 100% S n=8

Stops and timetable

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

Last 90 days, 57 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:25+1 min +1 min
19:39≈ 1 min early ≈ +1 min
19:49≈ 1 min early ≈ +1 min
19:582 min early +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 7 NovIlanz 19:54−2 min+4 min
Fri 6 NovIlanz 19:54−2 min+1 min
Thu 5 NovIlanz 19:57−2 min—
Wed 4 NovIlanz 19:54−2 min—
Tue 3 NovIlanz 19:54−2 min—
Mon 2 NovIlanz 19:58−1 min—
Sun 1 NovIlanz 19:54−2 min+4 min
Sat 31 OctIlanz 19:56−3 min+4 min
Fri 30 OctIlanz 19:56−3 min+1 min
Thu 29 OctIlanz 19:56−1 min—
Wed 28 OctIlanz 19:56−3 min+3 min
Tue 27 OctIlanz 19:56−3 min+4 min
Mon 26 OctIlanz 19:56−3 min—
Sun 25 OctIlanz 19:56−3 min—
Sat 24 OctIlanz 19:56−3 min+1 min
Fri 23 OctIlanz 19:56−3 min+2 min
Thu 22 OctIlanz 19:56−3 min+1 min
Wed 21 OctIlanz 19:57−2 min+1 min
Tue 20 OctIlanz 19:56−3 min+2 min
Mon 19 OctIlanz 19:56−3 min—
Sun 18 OctIlanz 19:57−3 min—
Sat 17 OctIlanz 19:58−1 min+1 min
Fri 16 OctIlanz 19:58−1 min—
Thu 15 OctIlanz 19:56−2 min—
Wed 14 OctIlanz 19:56−2 min+8 min
Tue 13 OctIlanz 19:56−3 min—
Mon 12 OctIlanz 19:56−3 min—
Sun 11 OctZürich HB 11:45+1 min+1 min
Sat 10 OctZürich HB 11:43−2 min—
Fri 9 OctIlanz 19:58−2 min+1 min