RE5 1754 Ilanz – Chur

View line RE5

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

✓ Today’s run finished

Today it reached Chur at 17:35 −1 min

  1. Ilanz17:00
  2. Valendas-Sagogn17:07
  3. Trin17:20
  4. Chur17:35

Next service: tomorrow 17:00 from Ilanz · Thu 12 Nov

Next departure 17:00 tomorrow · Ilanz
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
35/36 runs under 3 min
RT coverage: 36 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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 5 Oct Max en route +4 min · last fix heading to Chur +4 min

Distribution · 90 days

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

  • Early 36% · 13
  • On time 61% · 22
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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