R35 1306 Blonay → Vevey

View line R35

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

R35 1306 Blonay–Vevey: final delay under 3 min on 11 of its 12 runs with data in the last 30 days (92%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 14:13 (GMT+1).

✓ Today’s run finished

Today it reached Vevey at 06:55 −1 min

  1. Blonay06:40
  2. Château-de-Blonay06:41
  3. St-Légier-Village06:43
  4. St-Légier-Gare06:45
  5. Château-d'Hauteville06:47
  6. Vevey Vignerons06:49
  7. Vevey06:55

Next service: tomorrow 06:40 from Blonay · Sun 22 Nov

Next departure 06:40 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
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 18 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

  • Sat 24 Oct Max en route +15 min · last fix heading to Vevey +15 min

Distribution · 90 days

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

  • Early 17% · 5
  • On time 80% · 24
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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
06:40on time +1 min
06:41≈ on time ≈ +1 min
06:42≈ on time ≈ +1 min
06:43≈ on time ≈ +1 min
06:45 / 06:46≈ on time ≈ +1 min
06:47≈ on time ≈ +1 min
06:48≈ on time ≈ +1 min
06:49≈ on time ≈ +1 min
06: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
Sat 21 NovVevey 06:53−1 min—
Fri 20 NovVevey 06:58+2 min+2 min
Thu 19 NovVevey 06:570 min—
Wed 18 NovVevey 06:54+1 min—
Tue 17 NovVevey 06:57+1 min+1 min
Mon 16 NovVevey 06:54No data—
Sun 15 NovVevey 06:54No data—
Sat 14 NovVevey 06:54No data—
Fri 13 NovVevey 06:57No data—
Thu 12 NovVevey 06:55No data—
Wed 11 NovVevey 06:54No data—
Tue 10 NovVevey 06:54No data—
Mon 9 NovVevey 06:54No data—
Sun 8 NovVevey 06:55No data—
Sat 7 NovVevey 06:54No data—
Fri 6 NovVevey 06:54No data—
Thu 5 NovVevey 06:54No data—
Wed 4 NovVevey 06:54No data—
Tue 3 NovVevey 06:54No data—
Mon 2 NovVevey 06:54No data—
Sun 1 NovVevey 06:56No data—
Sat 31 OctVevey 06:56No data—
Fri 30 OctVevey 06:56No data—
Thu 29 OctVevey 06:55+1 min—
Wed 28 OctVevey 06:55+1 min—
Tue 27 OctVevey 06:55+1 min+1 min
Mon 26 OctVevey 06:570 min+1 min
Sun 25 OctVevey 06:560 min—
Sat 24 OctVevey 07:11+15 min+15 min
Fri 23 OctVevey 06:55−1 min—