R72 51 Champéry – Aigle

View line R72

Champéry 15:48 → Aigle 16:51 Daily 1 h 03 min · 24 stops TPC

✓ Today’s run finished

Today it reached Aigle at 16:53 +2 min

  1. Champéry15:48
  2. Val-d'Illiez15:58
  3. Route de Morgins16:11
  4. Monthey-Hôpital16:19
  5. Monthey-En Place16:31
  6. St-Triphon-Gare16:37
  7. Aigle16:51

Next service: tomorrow 15:48 from Champéry · Fri 13 Nov

Next departure 15:48 tomorrow · Champéry
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
97%
61/63 runs under 3 min
RT coverage: 63 full · 0 partial · 5 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Tue 13 Oct Max en route +22 min · last fix heading to Aigle +19 min
  • Thu 15 Oct Max en route +7 min · last fix heading to Aigle +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 61
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 91% T n=11
  • 100% W n=11
  • 89% T n=9
  • 100% F n=11
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 63 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:48on time on time
15:50≈ on time ≈ on time
15:54≈ on time ≈ on time
15:55≈ on time ≈ on time
15:58 / 15:59≈ on time ≈ on time
16:02≈ on time ≈ on time
16:03≈ on time ≈ on time
16:07 / 16:10≈ on time ≈ on time
16:11≈ on time ≈ +1 min
16:12≈ on time ≈ +1 min
16:13≈ on time ≈ +1 min
16:17≈ on time ≈ +1 min
16:19≈ on time ≈ +1 min
16:23≈ on time ≈ +1 min
16:25 / 16:29≈ on time ≈ +1 min
16:31≈ on time ≈ +1 min
16:33≈ on time ≈ +1 min
16:35≈ on time ≈ +1 min
16:36≈ on time ≈ +1 min
16:37≈ on time ≈ +1 min
16:39≈ on time ≈ +1 min
16:41≈ on time ≈ +1 min
16:44 / 16:45≈ on time ≈ +1 min
16:51on time +2 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 12 NovAigle 16:53+2 min+4 min
Wed 11 NovAigle 16:54+2 min+4 min
Tue 10 NovAigle 16:52+1 min+3 min
Mon 9 NovAigle 16:52+1 min+3 min
Sun 8 NovAigle 16:520 min+3 min
Sat 7 NovAigle 16:490 min+2 min
Fri 6 NovAigle 16:52+1 min+2 min
Thu 5 NovAigle 16:53+1 min+2 min
Wed 4 NovAigle 16:52+1 min+3 min
Tue 3 NovAigle 16:490 min+2 min
Mon 2 NovAigle 16:52−1 min+2 min
Sun 1 NovAigle 16:510 min+2 min
Sat 31 OctAigle 16:53+1 min+3 min
Fri 30 OctAigle 16:520 min+4 min
Thu 29 OctAigle 16:51+1 min+1 min
Wed 28 OctAigle 16:53+1 min+3 min
Tue 27 OctAigle 16:520 min+2 min
Mon 26 OctAigle 16:520 min+2 min
Sun 25 OctAigle 16:52No data—
Sat 24 OctAigle 16:520 min+1 min
Fri 23 OctAigle 16:530 min+2 min
Thu 22 OctAigle 16:52−1 min+1 min
Wed 21 OctAigle 16:54+2 min+3 min
Tue 20 OctAigle 16:52−1 min+2 min
Mon 19 OctAigle 16:53+1 min+4 min
Sun 18 OctAigle 16:51−1 min+1 min
Sat 17 OctAigle 16:510 min+1 min
Fri 16 OctAigle 16:54+2 min+5 min
Thu 15 OctAigle 16:57+5 min+7 min
Wed 14 OctAigle 16:510 min+2 min