SN 13844 Lausanne – Renens VD

View line SN

Lausanne 02:34 → Renens VD 02:39 Sat, Sun 0 h 05 min · 3 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Renens VD at 02:39 0 min

  1. Lausanne02:34
  2. Prilly-Malley02:37
  3. Renens VD02:39

Next service: Saturday 02:34 from Lausanne · Sat 21 Nov

Next departure 02:34 Saturday · Lausanne
On-time · 30 days
67%
6/9 runs under 3 min
RT coverage: 9 full · 0 partial · 1 no data
On-time · 90 days
73%
8/11 runs under 3 min
RT coverage: 11 full · 0 partial · 4 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+9min
9 in 10 runs arrive with less than this
30 days: +10 min

Last 30 days

Arrival delay at Renens VD, 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 1 Nov Max en route +13 min · last fix heading to Allaman +13 min
  • Sun 18 Oct Max en route +9 min · last fix heading to Allaman +9 min
  • Sun 8 Nov Max en route +4 min · last fix heading to Allaman +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 73% · 8
  • 3–10 min 18% · 2
  • 10–30 min 9% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 11 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
02:34on time +2 min
02:37≈ +1 min ≈ +6 min
02:39+1 min +9 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 NovRenens VD 02:390 min—
Sat 14 NovAllaman 02:590 min—
Sun 8 NovAllaman 03:02+4 min+4 min
Sat 7 NovAllaman 02:590 min—
Sun 1 NovAllaman 03:12+13 min+13 min
Sat 31 OctAllaman 03:00+1 min—
Sun 25 OctAllaman 02:59No data—
Sat 24 OctAllaman 02:590 min—
Sun 18 OctAllaman 03:09+9 min+9 min
Sat 17 OctAllaman 03:00+1 min+1 min
Sun 11 OctRenens VD 02:41+1 min—
Sat 10 OctAllaman 03:00No data—
Mon 5 OctAllaman 02:58No data—
Sun 4 OctAllaman 02:59No data—
Sat 5 SeptMorges 01:500 min+3 min