R35 1318 Blonay → Vevey

View line R35

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

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

✓ Today’s run finished

Today it reached Vevey at 09:56 +1 min

  1. Blonay09:40
  2. Château-de-Blonay09:41
  3. St-Légier-Village09:43
  4. St-Légier-Gare09:45
  5. Château-d'Hauteville09:47
  6. Vevey Vignerons09:49
  7. Vevey09:55

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

Next departure 09:40 tomorrow · Blonay
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
49/49 runs under 3 min
RT coverage: 49 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

  • Early 31% · 15
  • On time 69% · 34
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 100% S n=7
  • 100% S n=7

Stops and timetable

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

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