RE5 1735 Chur → Ilanz

View line RE5

Chur 11:25 → Ilanz 11:59 Daily 0 h 34 min · 4 stops RhB

RE5 1735 Chur–Ilanz: final delay under 3 min on 29 of its 30 runs with data in the last 30 days (97%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 17:55 (GMT+1).

✓ Today’s run finished

Today it reached Ilanz at 11:59 0 min

  1. Chur11:25
  2. Trin11:39
  3. Valendas-Sagogn11:49
  4. Ilanz11:59

Next service: tomorrow 11:25 from Chur · Mon 23 Nov

Next departure 11:25 tomorrow · Chur
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
60/62 runs under 3 min
RT coverage: 62 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 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 23 Oct Max en route +31 min · last fix heading to Genève-Aéroport +31 min
  • Thu 19 Nov Max en route +11 min · last fix heading to Brig +11 min

Distribution · 90 days

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

  • Early 3% · 2
  • On time 94% · 58
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=8
  • 100% T n=9
  • 100% W n=7
  • 88% T n=8
  • 90% F n=10
  • 100% S n=10
  • 100% S n=10

Stops and timetable

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

Last 90 days, 62 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
11:25on time on time
11:39≈ on time ≈ on time
11:49≈ on time ≈ +1 min
11:59on 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
Sun 22 NovIlanz 11:540 min—
Sat 21 NovBrig 22:030 min—
Fri 20 NovBrig 22:03+1 min—
Thu 19 NovBrig 22:14+11 min+11 min
Wed 18 NovBrig 22:020 min—
Tue 17 NovBrig 22:030 min—
Mon 16 NovBrig 22:03+2 min+2 min
Sun 15 NovBrig 22:030 min—
Sat 14 NovBrig 22:040 min—
Fri 13 NovBrig 22:030 min—
Thu 12 NovBrig 22:04+1 min—
Wed 11 NovBrig 22:030 min—
Tue 10 NovBrig 22:02−1 min—
Mon 9 NovBrig 22:02−1 min—
Sun 8 NovBrig 22:030 min—
Sat 7 NovBrig 22:030 min—
Fri 6 NovBrig 22:040 min—
Thu 5 NovBrig 22:020 min—
Wed 4 NovBrig 22:02−1 min—
Tue 3 NovBrig 22:030 min—
Mon 2 NovBrig 22:040 min—
Sun 1 NovVilleneuve VD 20:43+1 min+2 min
Sat 31 OctVilleneuve VD 20:42+1 min—
Fri 30 OctBrig 22:030 min—
Thu 29 OctBrig 22:02−1 min—
Wed 28 OctBrig 22:04+1 min—
Tue 27 OctBrig 22:030 min—
Mon 26 OctBrig 22:03−1 min—
Sun 25 OctBrig 22:01−2 min—
Sat 24 OctBrig 22:02−1 min—