RE7 1748 Ilanz – Chur

View line RE7

Ilanz 15:30 → Chur 16:05 Daily 0 h 35 min · 6 stops RhB

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 15:30 from Ilanz · Mon 9 Nov

Next departure 15:30 today · Ilanz
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
97%
38/39 runs under 3 min
RT coverage: 39 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 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

  • Sat 10 Oct Max en route +4 min · last fix heading to Reichenau-Tamins +4 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 95% · 37
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 39 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
15:30on time on time
15:33≈ on time ≈ on time
15:42 / 15:44≈ on time ≈ +1 min
15:55≈ on time ≈ +1 min
15:59≈ on time ≈ +1 min
16:05on 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 NovChur 16:040 min—
Sat 7 NovChur 16:04−1 min—
Fri 6 NovChur 16:04−1 min—
Thu 5 NovChur 16:040 min—
Wed 4 NovChur 16:04−1 min+1 min
Tue 3 NovChur 16:040 min—
Mon 2 NovChur 16:070 min+1 min
Sun 1 NovChur 16:060 min—
Sat 31 OctChur 16:06−1 min—
Fri 30 OctChur 16:050 min—
Thu 29 OctChur 16:05−1 min—
Wed 28 OctChur 16:060 min—
Tue 27 OctChur 16:07+1 min—
Mon 26 OctChur 16:070 min—
Sun 25 OctChur 16:07+1 min+1 min
Sat 24 OctChur 16:08+2 min+2 min
Fri 23 OctChur 16:07+1 min+1 min
Thu 22 OctChur 16:07+1 min—
Wed 21 OctChur 16:050 min—
Tue 20 OctChur 16:05−1 min—
Mon 19 OctChur 16:060 min—
Sun 18 OctChur 16:06+1 min+1 min
Sat 17 OctChur 16:06+1 min—
Fri 16 OctChur 16:070 min—
Thu 15 OctChur 16:060 min+1 min
Wed 14 OctChur 16:050 min—
Tue 13 OctChur 16:06No data—
Mon 12 OctChur 16:08+2 min+2 min
Sun 11 OctReichenau-Tamins 15:550 min—
Sat 10 OctReichenau-Tamins 16:00+4 min+4 min