R4 14423 Cossonay-Penthalaz – Lausanne

View line R4

Cossonay-Penthalaz 00:18 → Lausanne 00:33 Mon, Tue, Wed, Thu, Fri 0 h 15 min · 5 stops SBB CFF FFS

✓ Today’s run finished

Today, last fix heading to Le Day at 07:48 0 min

  1. Cossonay-Penthalaz00:18
  2. Bussigny00:23
  3. Renens VD00:25
  4. Prilly-Malley00:28
  5. Lausanne00:33

Next service: tomorrow 00:18 from Cossonay-Penthalaz · Fri 6 Nov

Next departure 00:18 tomorrow · Cossonay-Penthalaz
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 20 full · 2 partial · 0 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 26 full · 2 partial · 0 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: +2 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 28
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=5
  • 100% T n=6
  • 100% F n=4
  • 100% S n=1
  • — S n=0

Stops and timetable

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

Last 90 days, 28 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:18+1 min +1 min
00:23≈ +1 min ≈ +1 min
00:25 / 00:26≈ +1 min ≈ +1 min
00:28 / 00:29≈ on time ≈ +2 min
00: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 NovLe Day 07:48Partial coverage0 min—
Wed 4 NovLe Day 07:47+1 min—
Tue 3 NovLe Day 07:49Partial coverage0 min—
Mon 2 NovLe Day 07:490 min—
Fri 30 OctLe Day 07:51+3 min+3 min
Thu 29 OctLe Day 07:51+3 min+3 min
Wed 28 OctLe Day 07:49+1 min—
Tue 27 OctLe Day 07:480 min—
Mon 26 OctLe Day 07:490 min—
Fri 23 OctLe Day 07:480 min—
Thu 22 OctLe Day 07:47−1 min—
Wed 21 OctLe Day 07:49+1 min—
Tue 20 OctLe Day 07:50+1 min—
Mon 19 OctLe Day 07:47−1 min—
Fri 16 OctLe Day 07:49+1 min—
Thu 15 OctLe Day 07:480 min—
Wed 14 OctLe Day 07:47−1 min—
Tue 13 OctLe Day 07:480 min—
Mon 12 OctLe Day 07:470 min—
Fri 9 OctLe Day 07:49+2 min+2 min
Thu 8 OctLe Day 07:51+2 min+2 min
Wed 7 OctLe Day 07:470 min—
Tue 6 OctLe Day 07:49+1 min—
Mon 5 OctLe Day 07:480 min—
Tue 29 SeptLe Day 22:46+1 min+1 min
Mon 28 SeptLe Day 22:46+1 min—
Sat 19 SeptLe Day 22:44+2 min+2 min
Thu 13 AugLe Day 16:430 min—