R71 475 Les Diablerets – Aigle

View line R71

Les Diablerets 21:34 → Aigle 22:28 Daily 0 h 54 min · 18 stops TPC

It has not run yet today

Last recorded run: Tuesday 10 November −1 min

Next service: today 21:34 from Les Diablerets · Wed 11 Nov

Next departure 21:34 today · Les Diablerets
On-time · 30 days
79%
23/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
76%
32/42 runs under 3 min
RT coverage: 42 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Aigle, 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 3 Oct Max en route +15 min · last fix heading to Aigle +13 min
  • Tue 6 Oct Max en route +15 min · last fix heading to Aigle +13 min
  • Sun 18 Oct Max en route +11 min · last fix heading to Aigle +9 min
  • Sun 25 Oct Max en route +10 min · last fix heading to Aigle +8 min
  • Wed 7 Oct Max en route +10 min · last fix heading to Aigle +7 min

Distribution · 90 days

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

  • Early 17% · 7
  • On time 60% · 25
  • 3–10 min 19% · 8
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 83% T n=6
  • 80% W n=5
  • 83% T n=6
  • 86% F n=7
  • 83% S n=6
  • 50% S n=6

Stops and timetable

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

Last 90 days, 42 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
21:34on time +1 min
21:35≈ on time ≈ +1 min
21:36≈ on time ≈ +1 min
21:37≈ on time ≈ +1 min
21:38≈ on time ≈ +1 min
21:39≈ on time ≈ +1 min
21:40≈ on time ≈ +1 min
21:42≈ on time ≈ +1 min
21:44≈ on time ≈ +1 min
21:50≈ on time ≈ +2 min
21:53 / 21:57≈ +1 min ≈ +3 min
22:04≈ +1 min ≈ +4 min
22:09≈ +1 min ≈ +4 min
22:17≈ +1 min ≈ +5 min
22:20≈ +1 min ≈ +6 min
22:22≈ +1 min ≈ +6 min
22:24≈ +1 min ≈ +6 min
22:28+1 min +7 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
Tue 10 NovAigle 22:28−1 min+1 min
Mon 9 NovAigle 22:29−1 min+2 min
Sun 8 NovAigle 22:27−2 min—
Sat 7 NovAigle 22:28−1 min+3 min
Fri 6 NovAigle 22:27−1 min+4 min
Thu 5 NovAigle-Place-du-Marché 22:230 min+1 min
Wed 4 NovAigle 22:28−1 min+1 min
Tue 3 NovAigle 22:27−2 min+2 min
Mon 2 NovAigle 22:240 min—
Sun 1 NovAigle 22:28−1 min+2 min
Sat 31 OctAigle 22:290 min+4 min
Fri 30 OctAigle 22:27−2 min—
Thu 29 OctAigle 22:27−2 min—
Wed 28 OctAigle 22:26−3 min—
Tue 27 OctAigle 22:32+3 min+7 min
Mon 26 OctAigle 22:34+5 min+6 min
Sun 25 OctAigle 22:29+8 min+10 min
Sat 24 OctAigle 22:290 min+4 min
Fri 23 OctAigle 22:31+2 min+3 min
Thu 22 OctAigle 22:33+4 min+5 min
Wed 21 OctAigle 22:31+3 min+5 min
Tue 20 OctAigle 22:31+1 min+3 min
Mon 19 OctAigle 22:33+5 min+7 min
Sun 18 OctAigle 22:39+9 min+11 min
Sat 17 OctAigle 22:31+2 min+4 min
Fri 16 OctAigle 22:35+5 min+8 min
Thu 15 OctAigle 22:27−1 min+2 min
Wed 14 OctAigle 22:290 min+2 min
Tue 13 OctAigle 22:31+2 min+4 min
Mon 12 OctAigle 22:31+3 min+5 min