RE5 1758 Ilanz – Chur

View line RE5

Ilanz 18:00 → Chur 18:35 Daily 0 h 35 min · 4 stops RhB

It has not run yet today

Last recorded run: Thursday 5 November −2 min

Next service: today 18:00 from Ilanz · Fri 6 Nov

Next departure 18:00 today · Ilanz
On-time · 30 days
90%
26/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
91%
32/35 runs under 3 min
RT coverage: 35 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Mon 12 Oct Max en route +6 min · last fix heading to Chur +6 min
  • Tue 27 Oct Max en route +3 min · last fix heading to Chur +3 min
  • Fri 30 Oct Max en route +7 min · last fix heading to Chur +3 min

Distribution · 90 days

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

  • Early 14% · 5
  • On time 77% · 27
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 80% T n=5
  • 100% W n=5
  • 100% T n=5
  • 80% F n=5
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 35 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
18:00on time on time
18:07≈ on time ≈ +1 min
18:20≈ on time ≈ +2 min
18:35on time +3 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
Thu 5 NovChur 18:34−2 min+2 min
Wed 4 NovChur 18:39+3 min+4 min
Tue 3 NovChur 18:34−2 min+3 min
Mon 2 NovChur 18:370 min+2 min
Sun 1 NovChur 18:34−1 min—
Sat 31 OctChur 18:34−2 min—
Fri 30 OctChur 18:39+3 min+7 min
Thu 29 OctChur 18:360 min+4 min
Wed 28 OctChur 18:360 min+24 min
Tue 27 OctChur 18:40+3 min+3 min
Mon 26 OctChur 18:38+1 min+3 min
Sun 25 OctChur 18:38+3 min+3 min
Sat 24 OctChur 18:360 min+2 min
Fri 23 OctChur 18:38+2 min+2 min
Thu 22 OctChur 18:35−1 min+4 min
Wed 21 OctChur 18:38+2 min+4 min
Tue 20 OctChur 18:37+1 min+2 min
Mon 19 OctChur 18:35−1 min+2 min
Sun 18 OctChur 18:37+1 min+5 min
Sat 17 OctChur 18:37+1 min+3 min
Fri 16 OctChur 18:370 min—
Thu 15 OctChur 18:37+1 min+2 min
Wed 14 OctChur 18:36+1 min+3 min
Tue 13 OctChur 18:360 min+3 min
Mon 12 OctChur 18:42+6 min+6 min
Sun 11 OctBiel/Bienne 07:440 min—
Sat 10 OctBiel/Bienne 07:46+1 min+1 min
Fri 9 OctChur 18:37+1 min—
Thu 8 OctChur 18:350 min+1 min
Wed 7 OctChur 18:360 min—