R7 24788 Palézieux – Vevey

View line R7

Palézieux 00:11 → Vevey 00:30 Mon, Fri, Sat, Sun 0 h 19 min · 4 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Vevey at 00:30 0 min

  1. Palézieux00:11
  2. Puidoux00:17
  3. Chexbres-Village00:21
  4. Vevey00:30

Next service: Friday 00:11 from Palézieux · Fri 20 Nov

Next departure 00:11 Friday · Palézieux
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
On-time · 90 days
98%
39/40 runs under 3 min
RT coverage: 40 full · 0 partial · 1 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: +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 17 Oct Max en route +6 min · last fix heading to Vevey +6 min

Distribution · 90 days

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

  • Early 18% · 7
  • On time 80% · 32
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=3
  • 88% S n=8
  • 100% S n=10

Stops and timetable

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

Last 90 days, 40 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
00:11on time +1 min
00:17≈ on time ≈ +1 min
00:21≈ on time ≈ +1 min
00:30on 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
Sun 15 NovVevey 00:290 min—
Sat 14 NovVevey 00:32+1 min—
Sun 8 NovVevey 00:32+1 min+1 min
Sat 7 NovVevey 00:33+1 min+1 min
Sun 1 NovVevey 00:30−1 min—
Sat 31 OctVevey 00:310 min—
Sat 24 OctVevey 00:32+1 min—
Sun 18 OctVevey 00:32+1 min+1 min
Sat 17 OctVevey 00:37+6 min+6 min
Sun 11 OctVevey 00:30−1 min—
Sat 10 OctVevey 00:320 min—
Mon 5 OctVevey 00:31No data—
Sun 4 OctVevey 00:270 min—
Thu 1 OctVevey 00:30−1 min—
Wed 30 SeptVevey 00:290 min—
Tue 29 SeptVevey 00:29+1 min+1 min
Sun 27 SeptVevey 00:29−1 min+1 min
Thu 24 SeptVevey 00:290 min—
Wed 23 SeptVevey 00:300 min+3 min
Tue 22 SeptVevey 00:290 min+3 min
Mon 21 SeptVevey 00:29−1 min—
Sun 20 SeptVevey 00:290 min+5 min
Sat 19 SeptVevey 00:30−1 min+2 min
Fri 18 SeptVevey 00:29−1 min—
Thu 17 SeptVevey 00:29−1 min—
Wed 16 SeptVevey 00:29−2 min+1 min
Tue 15 SeptVevey 00:29−3 min+2 min
Mon 14 SeptVevey 00:30−2 min+4 min
Wed 9 SeptVevey 00:290 min+4 min
Tue 8 SeptVevey 00:30+1 min—