R35 1543 Vevey – Blonay

View line R35

Vevey 16:20 → Blonay 16:36 Mon, Tue, Wed, Thu, Fri 0 h 16 min · 9 stops MVR

✓ Today’s run finished

Today it reached Blonay at 16:37 +1 min

  1. Vevey16:20
  2. Vevey Vignerons16:23
  3. Château-d'Hauteville16:26
  4. St-Légier-Gare16:29
  5. St-Légier-Village16:31
  6. Château-de-Blonay16:33
  7. Blonay16:36

Next service: tomorrow 16:20 from Vevey · Thu 19 Nov

Next departure 16:20 tomorrow · Vevey
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
98%
48/49 runs under 3 min
RT coverage: 49 full · 0 partial · 1 no data
Typical delay
+1min
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 Blonay, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 28 Aug Max en route +10 min · last fix heading to Château-d'Hauteville +10 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 96% · 47
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=8
  • 100% T n=6
  • 86% F n=7
  • 100% S n=6
  • 100% S n=8

Stops and timetable

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

Last 90 days, 49 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
16:20on time on time
16:23≈ on time ≈ on time
16:25≈ on time ≈ +1 min
16:26≈ on time ≈ +1 min
16:29 / 16:30≈ on time ≈ +1 min
16:31≈ on time ≈ +2 min
16:32≈ on time ≈ +2 min
16:33≈ on time ≈ +2 min
16:36+1 min +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
Wed 18 NovBlonay 16:38+1 min+2 min
Tue 17 NovBlonay 16:38+1 min+1 min
Mon 16 NovBlonay 16:39+2 min+2 min
Sun 15 NovThusis 10:19−1 min—
Sat 14 NovThusis 10:19−1 min—
Fri 13 NovBlonay 16:370 min+1 min
Thu 12 NovBlonay 16:370 min+3 min
Wed 11 NovBlonay 16:370 min+2 min
Tue 10 NovBlonay 16:370 min+1 min
Mon 9 NovBlonay 16:370 min—
Sun 8 NovThusis 10:19+1 min+1 min
Sat 7 NovThusis 10:190 min—
Fri 6 NovBlonay 16:370 min+2 min
Thu 5 NovBlonay 16:37+1 min+2 min
Wed 4 NovBlonay 16:370 min—
Tue 3 NovBlonay 16:370 min—
Mon 2 NovBlonay 16:37+1 min+1 min
Sun 1 NovThusis 10:19−1 min—
Sat 31 OctThusis 10:19−1 min—
Fri 30 OctBlonay 16:370 min—
Thu 29 OctBlonay 16:37No data—
Wed 28 OctBlonay 16:40+3 min+3 min
Tue 27 OctBlonay 16:39+2 min+2 min
Mon 26 OctBlonay 16:39+1 min+2 min
Sun 25 OctThusis 10:19−1 min—
Sat 24 OctThusis 10:200 min—
Fri 23 OctBlonay 16:370 min+2 min
Thu 22 OctBlonay 16:38+1 min+1 min
Wed 21 OctBlonay 16:39+2 min+2 min
Tue 20 OctBlonay 16:38+1 min—