R71 479 Les Diablerets – Aigle

View line R71

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

It has not run yet today

Last recorded run: Friday 13 November −3 min

Next service: today 22:34 from Les Diablerets · Sat 14 Nov

Next departure 22:34 today · Les Diablerets
On-time · 30 days
72%
21/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
72%
34/47 runs under 3 min
RT coverage: 47 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Thu 5 Nov Max en route +27 min · last fix heading to Aigle +26 min
  • Sun 18 Oct Max en route +10 min · last fix heading to Aigle +10 min
  • Wed 7 Oct Max en route +9 min · last fix heading to Aigle +8 min
  • Sat 3 Oct Max en route +9 min · last fix heading to Aigle +7 min
  • Fri 16 Oct Max en route +7 min · last fix heading to Aigle +5 min

Distribution · 90 days

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

  • Early 19% · 9
  • On time 53% · 25
  • 3–10 min 23% · 11
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 33% M n=6
  • 100% T n=6
  • 83% W n=6
  • 67% T n=6
  • 89% F n=9
  • 43% S n=7
  • 86% S n=7

Stops and timetable

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

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