R35 1341 Vevey – Blonay

View line R35

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

It has not run yet today

Last recorded run: Friday 13 November No data

Next service: today 15:35 from Vevey · Sat 14 Nov

Next departure 15:35 today · Vevey
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 15 full · 0 partial · 14 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 27 full · 0 partial · 14 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+3min
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

  • Sat 24 Oct Max en route +21 min · last fix heading to Blonay +21 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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