RE7 1757 Chur – Ilanz

View line RE7

Chur 16:55 → Ilanz 17:29 Daily 0 h 34 min · 6 stops RhB

It has not run yet today

Last recorded run: Monday 16 November +5 min

Next service: today 16:55 from Chur · Tue 17 Nov

Next departure 16:55 today · Chur
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
91%
48/53 runs under 3 min
RT coverage: 53 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

  • Mon 16 Nov Max en route +5 min · last fix heading to Ilanz +5 min
  • Thu 15 Oct Max en route +4 min · last fix heading to Ilanz +4 min
  • Sat 3 Oct Max en route +4 min · last fix heading to Castrisch +4 min
  • Mon 5 Oct Max en route +4 min · last fix heading to Ilanz +4 min
  • Mon 14 Sept Max en route +4 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 36% · 19
  • On time 55% · 29
  • 3–10 min 9% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 53 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
16:55+1 min +1 min
17:00≈ on time ≈ +1 min
17:04≈ on time ≈ +1 min
17:15 / 17:16≈ on time ≈ +1 min
17:25≈ on time ≈ +1 min
17:29on 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
Mon 16 NovIlanz 17:34+5 min+5 min
Sun 15 NovIlanz 17:280 min—
Sat 14 NovIlanz 17:29+1 min+1 min
Fri 13 NovIlanz 17:32+1 min+4 min
Thu 12 NovIlanz 17:29−1 min+5 min
Wed 11 NovIlanz 17:29−1 min+1 min
Tue 10 NovIlanz 17:29−1 min+4 min
Mon 9 NovIlanz 17:290 min+2 min
Sun 8 NovIlanz 17:290 min—
Sat 7 NovIlanz 17:28−2 min+2 min
Fri 6 NovIlanz 17:280 min+2 min
Thu 5 NovIlanz 17:280 min+2 min
Wed 4 NovIlanz 17:29−2 min+1 min
Tue 3 NovIlanz 17:290 min—
Mon 2 NovIlanz 17:29−2 min+2 min
Sun 1 NovIlanz 17:28−2 min+2 min
Sat 31 OctIlanz 17:280 min—
Fri 30 OctIlanz 17:300 min+2 min
Thu 29 OctIlanz 17:280 min+1 min
Wed 28 OctIlanz 17:290 min+6 min
Tue 27 OctIlanz 17:300 min+1 min
Mon 26 OctIlanz 17:29−2 min+2 min
Sun 25 OctIlanz 17:28−2 min+2 min
Sat 24 OctIlanz 17:28−2 min+3 min
Fri 23 OctIlanz 17:29−1 min+2 min
Thu 22 OctIlanz 17:29−1 min+2 min
Wed 21 OctIlanz 17:30+1 min+9 min
Tue 20 OctIlanz 17:290 min+3 min
Mon 19 OctIlanz 17:300 min+3 min
Sun 18 OctIlanz 17:29−1 min—