R4 24415 Le Day – Lausanne

View line R4

Le Day 05:52 → Lausanne 06:33 Daily 0 h 41 min · 9 stops SBB CFF FFS

✓ Today’s run finished

Today, last fix heading to Vevey at 06:59 +2 min

  1. Le Day05:52
  2. Croy-Romainmôtier06:00
  3. La Sarraz06:10
  4. Cossonay-Penthalaz06:17
  5. Bussigny06:22
  6. Prilly-Malley06:29
  7. Lausanne06:33

Next service: tomorrow 05:52 from Le Day · Fri 6 Nov

Next departure 05:52 tomorrow · Le Day
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 27 full · 2 partial · 1 no data
On-time · 90 days
94%
49/52 runs under 3 min
RT coverage: 50 full · 2 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Lausanne, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 18 Oct Max en route +12 min · last fix heading to Vevey +12 min
  • Sun 25 Oct Max en route +8 min · last fix heading to Vevey +8 min
  • Tue 11 Aug Max en route +4 min · last fix heading to Vevey +4 min

Distribution · 90 days

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

  • Early 6% · 3
  • On time 88% · 46
  • 3–10 min 4% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 90% T n=10
  • 100% W n=9
  • 100% T n=5
  • 100% F n=8
  • 100% S n=7
  • 71% S n=7

Stops and timetable

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

Last 90 days, 52 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:52on time +1 min
06:00≈ on time ≈ +1 min
06:05≈ on time ≈ +1 min
06:10≈ on time ≈ +1 min
06:17≈ on time ≈ +2 min
06:22≈ on time ≈ +1 min
06:25 / 06:26≈ on time ≈ +1 min
06:29≈ on time ≈ +2 min
06:33on time +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
Thu 5 NovVevey 06:59Partial coverage+2 min+2 min
Wed 4 NovVevey 06:59Partial coverage+3 min+4 min
Tue 3 NovVevey 06:59+3 min+3 min
Mon 2 NovVevey 06:580 min—
Sun 1 NovCully 06:48−1 min—
Sat 31 OctCully 06:48−1 min—
Fri 30 OctVevey 06:570 min+1 min
Thu 29 OctVevey 06:58+1 min—
Wed 28 OctVevey 06:570 min—
Tue 27 OctVevey 06:570 min—
Mon 26 OctVevey 06:570 min—
Sun 25 OctVevey 07:04+8 min+8 min
Sat 24 OctVevey 06:59+2 min+2 min
Fri 23 OctVevey 06:570 min—
Thu 22 OctVevey 07:00+3 min+4 min
Wed 21 OctVevey 06:58+1 min—
Tue 20 OctVevey 06:580 min—
Mon 19 OctVevey 06:58+1 min+1 min
Sun 18 OctVevey 07:07+12 min+12 min
Sat 17 OctVevey 06:57No data—
Fri 16 OctVevey 06:570 min—
Thu 15 OctVevey 06:570 min—
Wed 14 OctVevey 06:570 min—
Tue 13 OctVevey 06:58+1 min—
Mon 12 OctVevey 06:570 min—
Sun 11 OctVevey 06:570 min—
Sat 10 OctVevey 06:59+2 min+3 min
Fri 9 OctVevey 06:59+2 min+2 min
Thu 8 OctVevey 06:570 min—
Wed 7 OctVevey 06:58+1 min+3 min