R35 1405 Vevey → Blonay

View line R35

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

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

✓ Today’s run finished

Today it reached Blonay at 06:51 0 min

  1. Vevey06:35
  2. Vevey Vignerons06:38
  3. Château-d'Hauteville06:41
  4. St-Légier-Gare06:44
  5. St-Légier-Village06:46
  6. Château-de-Blonay06:48
  7. Blonay06:51

Next service: tomorrow 06:35 from Vevey · Sun 22 Nov

Next departure 06:35 tomorrow · Vevey
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 12 full · 0 partial · 18 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 31 full · 0 partial · 18 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: +1 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

  • Tue 13 Oct Max en route +6 min · last fix heading to Lally +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 30
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 80% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • 100% 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, 31 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:35+1 min +1 min
06:38≈ +1 min ≈ +1 min
06:40≈ +1 min ≈ +1 min
06:41≈ +1 min ≈ +1 min
06:44 / 06:45≈ +1 min ≈ +1 min
06:46≈ +1 min ≈ +2 min
06:47≈ +1 min ≈ +2 min
06:48≈ +1 min ≈ +2 min
06: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
Sat 21 NovBlonay 06:520 min—
Fri 20 NovLally 07:07+1 min+1 min
Thu 19 NovLally 07:08+1 min—
Wed 18 NovLally 07:08+1 min+2 min
Tue 17 NovLally 07:09+1 min+3 min
Mon 16 NovLally 07:07No data—
Sun 15 NovBlonay 06:52No data—
Sat 14 NovBlonay 06:52No data—
Fri 13 NovLally 07:08No data—
Thu 12 NovLally 07:08No data—
Wed 11 NovLally 07:07No data—
Tue 10 NovLally 07:07No data—
Mon 9 NovLally 07:07No data—
Sun 8 NovBlonay 06:53No data—
Sat 7 NovBlonay 06:52No data—
Fri 6 NovLally 07:07No data—
Thu 5 NovLally 07:07No data—
Wed 4 NovLally 07:07No data—
Tue 3 NovLally 07:07No data—
Mon 2 NovLally 07:07No data—
Sun 1 NovBlonay 06:52No data—
Sat 31 OctBlonay 06:52No data—
Fri 30 OctLally 07:07No data—
Thu 29 OctLally 07:09+2 min+2 min
Wed 28 OctLally 07:08+1 min—
Tue 27 OctLally 07:09+1 min+2 min
Mon 26 OctLally 07:08+1 min+2 min
Sun 25 OctBlonay 06:53+1 min—
Sat 24 OctBlonay 06:53+1 min—
Fri 23 OctLally 07:08+1 min—