R3 24313 Vallorbe – Vevey

View line R3

Vallorbe 05:16 → Vevey 06:22 Daily 1 h 06 min · 15 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Vevey at 06:22 0 min

  1. Vallorbe05:16
  2. Bretonnières05:27
  3. La Sarraz05:40
  4. Bussigny05:52
  5. Prilly-Malley05:59
  6. Lutry06:10
  7. Vevey06:22

Next service: tomorrow 05:16 from Vallorbe · Sat 7 Nov

Next departure 05:16 tomorrow · Vallorbe
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
43/44 runs under 3 min
RT coverage: 44 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

  • Fri 30 Oct Max en route +23 min · last fix heading to Vevey +23 min

Distribution · 90 days

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

  • Early 9% · 4
  • On time 89% · 39
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=7
  • 100% W n=6
  • 100% T n=6
  • 80% F n=5
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

Last 90 days, 44 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
05:16on time on time
05:20 / 05:21≈ on time ≈ on time
05:27≈ on time ≈ on time
05:30≈ on time ≈ on time
05:35≈ on time ≈ on time
05:40≈ on time ≈ on time
05:47≈ on time ≈ +1 min
05:52≈ on time ≈ +1 min
05:55 / 05:56≈ on time ≈ +1 min
05:59≈ on time ≈ +1 min
06:03 / 06:04≈ on time ≈ +1 min
06:07≈ on time ≈ +1 min
06:10≈ on time ≈ +1 min
06:13≈ on time ≈ +1 min
06:22on 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
Fri 6 NovVevey 06:230 min—
Thu 5 NovVevey 06:230 min—
Wed 4 NovVevey 06:24+1 min—
Tue 3 NovVevey 06:22−1 min—
Mon 2 NovVevey 06:24+1 min—
Sun 1 NovCully 06:16+2 min+2 min
Sat 31 OctCully 06:16+2 min+2 min
Fri 30 OctVevey 06:23+23 min+23 min
Thu 29 OctVevey 06:230 min—
Wed 28 OctVevey 06:22−1 min—
Tue 27 OctVevey 06:230 min—
Mon 26 OctVevey 06:22−1 min—
Sun 25 OctVevey 06:22−1 min—
Sat 24 OctVevey 06:230 min—
Fri 23 OctVevey 06:230 min—
Thu 22 OctVevey 06:22−1 min—
Wed 21 OctVevey 06:25+2 min+2 min
Tue 20 OctVevey 06:22−1 min—
Mon 19 OctVevey 06:230 min—
Sun 18 OctVevey 06:23−1 min—
Sat 17 OctVevey 06:230 min+2 min
Fri 16 OctVevey 06:230 min—
Thu 15 OctVevey 06:230 min—
Wed 14 OctVevey 06:22−1 min—
Tue 13 OctVevey 06:24+1 min+1 min
Mon 12 OctVevey 06:22−1 min—
Sun 11 OctVevey 06:22−1 min—
Sat 10 OctVevey 06:240 min—
Fri 9 OctVevey 06:230 min—
Thu 8 OctVevey 06:230 min—