R35 1345 Vevey – Blonay

View line R35

Vevey 16:35 → Blonay 16:51 Daily 0 h 16 min · 9 stops MVR

✓ Today’s run finished

Today it reached Blonay at 16:52 +1 min

  1. Vevey16:35
  2. Vevey Vignerons16:38
  3. Château-d'Hauteville16:41
  4. St-Légier-Gare16:44
  5. St-Légier-Village16:46
  6. Château-de-Blonay16:48
  7. Blonay16:51

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

Next departure 16:35 tomorrow · Vevey
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 11 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 35 full · 0 partial · 11 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

Distribution · 90 days

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

  • Early 11% · 4
  • On time 89% · 31
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=3
  • 100% F n=4
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 35 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:35+1 min +1 min
16:38≈ +1 min ≈ +2 min
16:40≈ +1 min ≈ +2 min
16:41≈ +1 min ≈ +2 min
16:44 / 16:45≈ +1 min ≈ +2 min
16:46≈ +1 min ≈ +2 min
16:47≈ +1 min ≈ +2 min
16:48≈ +1 min ≈ +2 min
16:51+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:53+1 min—
Tue 17 NovBlonay 16:54+2 min+2 min
Mon 16 NovBlonay 16:53+1 min—
Sun 15 NovBlonay 16:52−2 min—
Sat 14 NovBlonay 16:520 min—
Fri 13 NovBlonay 16:52No data—
Thu 12 NovBlonay 16:52No data—
Wed 11 NovBlonay 16:52No data—
Tue 10 NovBlonay 16:52No data—
Mon 9 NovBlonay 16:52No data—
Sun 8 NovBlonay 16:52−1 min—
Sat 7 NovBlonay 16:520 min—
Fri 6 NovBlonay 16:52No data—
Thu 5 NovBlonay 16:52No data—
Wed 4 NovBlonay 16:52No data—
Tue 3 NovBlonay 16:52No data—
Mon 2 NovBlonay 16:52No data—
Sun 1 NovBlonay 16:520 min—
Sat 31 OctBlonay 16:52−1 min—
Fri 30 OctBlonay 16:52−2 min—
Thu 29 OctBlonay 16:52No data—
Wed 28 OctBlonay 16:53+1 min—
Tue 27 OctBlonay 16:53+1 min—
Mon 26 OctBlonay 16:54+2 min+2 min
Sun 25 OctBlonay 16:53+2 min+2 min
Sat 24 OctBlonay 16:54+2 min+2 min
Fri 23 OctBlonay 16:53+2 min+3 min
Thu 22 OctBlonay 16:53+1 min—
Wed 21 OctBlonay 16:54+2 min+2 min
Tue 20 OctBlonay 16:54+2 min+2 min