RE7 1717 Chur – Ilanz

View line RE7

Chur 06:53 → Ilanz 07:30 Daily 0 h 37 min · 10 stops RhB

✓ Today’s run finished

Today it reached Ilanz at 07:30 −1 min

  1. Chur06:53
  2. Domat/Ems07:00
  3. Domat/Ems Werk07:02
  4. Trin07:11
  5. Versam-Safien07:17
  6. Castrisch07:27
  7. Ilanz07:30

Next service: tomorrow 06:53 from Chur · Mon 9 Nov

Next departure 06:53 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
96%
48/50 runs under 3 min
RT coverage: 50 full · 0 partial · 0 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

  • Tue 15 Sept Max en route +24 min · last fix heading to Leuk +24 min
  • Sun 1 Nov Max en route +3 min · last fix heading to Villeneuve VD +3 min

Distribution · 90 days

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

  • Early 6% · 3
  • On time 90% · 45
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 50 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
06:53on time on time
06:55≈ on time ≈ on time
07:00≈ on time ≈ on time
07:02≈ on time ≈ on time
07:05≈ on time ≈ +1 min
07:11 / 07:12≈ on time ≈ +1 min
07:17≈ on time ≈ +1 min
07:22≈ on time ≈ +1 min
07:27 / 07:28≈ on time ≈ +1 min
07:30on 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 8 NovIlanz 07:30−1 min—
Sat 7 NovBrig 13:02−1 min+2 min
Fri 6 NovBrig 13:03−1 min+2 min
Thu 5 NovBrig 13:030 min+2 min
Wed 4 NovBrig 13:030 min+2 min
Tue 3 NovBrig 13:03−1 min+2 min
Mon 2 NovBrig 13:030 min—
Sun 1 NovVilleneuve VD 11:45+3 min+3 min
Sat 31 OctVilleneuve VD 11:44+2 min+3 min
Fri 30 OctBrig 13:02−1 min—
Thu 29 OctBrig 13:03+1 min+1 min
Wed 28 OctBrig 13:03−1 min+1 min
Tue 27 OctBrig 13:030 min—
Mon 26 OctBrig 13:030 min+2 min
Sun 25 OctBrig 13:030 min+1 min
Sat 24 OctBrig 13:02−1 min—
Fri 23 OctBrig 13:02−1 min—
Thu 22 OctBrig 13:030 min—
Wed 21 OctBrig 13:05+2 min+2 min
Tue 20 OctBrig 13:03−1 min+1 min
Mon 19 OctBrig 13:030 min+1 min
Sun 18 OctBrig 13:050 min—
Sat 17 OctBrig 13:04+1 min+2 min
Fri 16 OctBrig 13:02−1 min+1 min
Thu 15 OctBrig 13:030 min—
Wed 14 OctBrig 13:02−1 min—
Tue 13 OctBrig 13:03−1 min—
Mon 12 OctBrig 13:030 min+2 min
Sun 11 OctBrig 13:03−1 min+1 min
Sat 10 OctBrig 13:03−1 min+3 min