R35 1300 Blonay – Vevey

View line R35

Blonay 05:10 → Vevey 05:25 Daily 0 h 15 min · 9 stops MVR

✓ Today’s run finished

Today it reached Vevey at 05:25 −2 min

  1. Blonay05:10
  2. Château-de-Blonay05:11
  3. St-Légier-Village05:13
  4. St-Légier-Gare05:15
  5. Château-d'Hauteville05:17
  6. Vevey Vignerons05:19
  7. Vevey05:25

Next service: tomorrow 05:10 from Blonay · Thu 19 Nov

Next departure 05:10 tomorrow · Blonay
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 12 full · 0 partial · 18 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 28 full · 0 partial · 18 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Vevey, 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 23 Oct Max en route +7 min · last fix heading to Vevey +7 min
  • Thu 8 Oct Max en route +3 min · last fix heading to Vevey +3 min

Distribution · 90 days

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

  • Early 54% · 15
  • On time 39% · 11
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
05:10on time +1 min
05:11≈ on time ≈ +1 min
05:12≈ on time ≈ +1 min
05:13≈ on time ≈ +1 min
05:15 / 05:16≈ on time ≈ +1 min
05:17≈ on time ≈ +1 min
05:18≈ on time ≈ +1 min
05:19≈ on time ≈ +1 min
05:251 min early on time

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 NovVevey 05:24−2 min—
Tue 17 NovVevey 05:230 min—
Mon 16 NovVevey 05:24No data—
Sun 15 NovVevey 05:24No data—
Sat 14 NovVevey 05:24No data—
Fri 13 NovVevey 05:27No data—
Thu 12 NovVevey 05:24No data—
Wed 11 NovVevey 05:24No data—
Tue 10 NovVevey 05:24No data—
Mon 9 NovVevey 05:24No data—
Sun 8 NovVevey 05:23No data—
Sat 7 NovVevey 05:24No data—
Fri 6 NovVevey 05:24No data—
Thu 5 NovVevey 05:24No data—
Wed 4 NovVevey 05:24No data—
Tue 3 NovVevey 05:24No data—
Mon 2 NovVevey 05:24No data—
Sun 1 NovVevey 05:26No data—
Sat 31 OctVevey 05:26No data—
Fri 30 OctVevey 05:26No data—
Thu 29 OctVevey 05:25−1 min—
Wed 28 OctVevey 05:26−1 min—
Tue 27 OctVevey 05:24−2 min—
Mon 26 OctVevey 05:230 min—
Sun 25 OctVevey 05:24−2 min—
Sat 24 OctVevey 05:25−1 min—
Fri 23 OctVevey 05:32+7 min+7 min
Thu 22 OctVevey 05:270 min+3 min
Wed 21 OctVevey 05:240 min—
Tue 20 OctVevey 05:24−2 min—