R35 1326 Blonay – Vevey

View line R35

Blonay 11:40 → Vevey 11:55 Daily 0 h 15 min · 9 stops MVR

✓ Today’s run finished

Today it reached Vevey at 11:56 +1 min

  1. Blonay11:40
  2. Château-de-Blonay11:41
  3. St-Légier-Village11:43
  4. St-Légier-Gare11:45
  5. Château-d'Hauteville11:47
  6. Vevey Vignerons11:49
  7. Vevey11:55

Next service: tomorrow 11:40 from Blonay · Sat 21 Nov

Next departure 11:40 tomorrow · Blonay
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
47/48 runs under 3 min
RT coverage: 48 full · 0 partial · 0 no data
Typical delay
0min
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 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

  • Tue 3 Nov Max en route +4 min · last fix heading to Vevey +4 min

Distribution · 90 days

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

  • Early 31% · 15
  • On time 67% · 32
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 86% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 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, 48 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
11:40on time +1 min
11:41≈ on time ≈ on time
11:42≈ on time ≈ on time
11:43≈ on time ≈ +1 min
11:45 / 11:46≈ on time ≈ +1 min
11:47≈ on time ≈ +1 min
11:48≈ on time ≈ +1 min
11:49≈ on time ≈ +1 min
11:55on 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
Fri 20 NovVevey 11:54+1 min+3 min
Thu 19 NovVevey 11:54+3 min+3 min
Wed 18 NovVevey 11:540 min—
Tue 17 NovVevey 11:57+1 min+3 min
Mon 16 NovVevey 11:54−1 min—
Sun 15 NovVevey 11:54−1 min+1 min
Sat 14 NovVevey 11:54−2 min—
Fri 13 NovVevey 11:54+2 min+3 min
Thu 12 NovVevey 11:54+2 min+3 min
Wed 11 NovVevey 11:54−1 min—
Tue 10 NovVevey 11:54−1 min+2 min
Mon 9 NovVevey 11:54−2 min—
Sun 8 NovVevey 11:54−1 min—
Sat 7 NovVevey 11:540 min+3 min
Fri 6 NovVevey 11:54−1 min+3 min
Thu 5 NovVevey 11:54−1 min—
Wed 4 NovVevey 11:54−1 min—
Tue 3 NovVevey 11:54+4 min+4 min
Mon 2 NovVevey 11:540 min—
Sun 1 NovVevey 11:56−1 min+1 min
Sat 31 OctVevey 11:56−1 min—
Fri 30 OctVevey 11:56−2 min—
Thu 29 OctVevey 11:56+1 min+1 min
Wed 28 OctVevey 11:550 min—
Tue 27 OctVevey 11:540 min+1 min
Mon 26 OctVevey 11:57−1 min—
Sun 25 OctVevey 11:55−1 min+3 min
Sat 24 OctVevey 11:57+1 min+3 min
Fri 23 OctVevey 11:55+1 min—
Thu 22 OctVevey 11:56+1 min+1 min