R35 1317 Vevey → Blonay

View line R35

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

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

✓ Today’s run finished

Today it reached Blonay at 09:53 +2 min

  1. Vevey09:35
  2. Vevey Vignerons09:38
  3. Château-d'Hauteville09:41
  4. St-Légier-Gare09:44
  5. St-Légier-Village09:46
  6. Château-de-Blonay09:48
  7. Blonay09:51

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

Next departure 09:35 tomorrow · Vevey
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 10 full · 0 partial · 20 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 20 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+2min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 29
  • 3–10 min 0% · 0
  • 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
  • 100% T n=3
  • 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, 29 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
09:35+1 min +1 min
09:38≈ +1 min ≈ +1 min
09:40≈ +1 min ≈ +1 min
09:41≈ +1 min ≈ +2 min
09:44 / 09:45≈ +1 min ≈ +2 min
09:46≈ +1 min ≈ +2 min
09:47≈ +1 min ≈ +2 min
09:48≈ +1 min ≈ +2 min
09:51+2 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 09:53+2 min+2 min
Fri 20 NovBlonay 09:53+1 min+2 min
Thu 19 NovBlonay 09:52No data—
Wed 18 NovBlonay 09:54+2 min+2 min
Tue 17 NovBlonay 09:54+3 min+3 min
Mon 16 NovBlonay 09:52No data—
Sun 15 NovBlonay 09:52No data—
Sat 14 NovBlonay 09:52No data—
Fri 13 NovBlonay 09:52No data—
Thu 12 NovBlonay 09:52No data—
Wed 11 NovBlonay 09:52No data—
Tue 10 NovBlonay 09:52No data—
Mon 9 NovBlonay 09:52No data—
Sun 8 NovBlonay 09:52No data—
Sat 7 NovBlonay 09:52No data—
Fri 6 NovBlonay 09:52No data—
Thu 5 NovBlonay 09:52No data—
Wed 4 NovBlonay 09:52No data—
Tue 3 NovBlonay 09:52No data—
Mon 2 NovBlonay 09:52No data—
Sun 1 NovBlonay 09:52No data—
Sat 31 OctBlonay 09:52No data—
Fri 30 OctBlonay 09:52No data—
Thu 29 OctBlonay 09:52No data—
Wed 28 OctBlonay 09:54+2 min+2 min
Tue 27 OctBlonay 09:54+1 min+2 min
Mon 26 OctBlonay 09:53+1 min—
Sun 25 OctBlonay 09:53+2 min+2 min
Sat 24 OctBlonay 09:54+2 min+2 min
Fri 23 OctBlonay 09:53+2 min+2 min