R4 14493 Vallorbe – Le Day

View line R4

Vallorbe 22:42 → Le Day 22:47 Mon, Tue, Wed, Thu, Fri 0 h 05 min · 2 stops SBB CFF FFS

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 22:42 from Vallorbe · Fri 6 Nov

Next departure 22:42 today · Vallorbe
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
94%
30/32 runs under 3 min
RT coverage: 32 full · 0 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 Le Day, in minutes. One bar per run.

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

Worst days

  • Tue 13 Oct Max en route +4 min · last fix heading to Le Day +4 min
  • Tue 20 Oct Max en route +3 min · last fix heading to Le Day +3 min

Distribution · 90 days

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

  • Early 22% · 7
  • On time 72% · 23
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 75% T n=8
  • 100% W n=7
  • 100% T n=6
  • 100% F n=4
  • — S n=0
  • 100% S n=1

Stops and timetable

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

Last 90 days, 32 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
22:42+1 min +1 min
22:47on 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 22:480 min—
Wed 4 NovLe Day 22:47−1 min—
Tue 3 NovLe Day 22:49+1 min+1 min
Mon 2 NovLe Day 22:480 min—
Fri 30 OctLe Day 22:50+2 min+2 min
Thu 29 OctLe Day 22:480 min—
Wed 28 OctLe Day 22:47−1 min—
Tue 27 OctLe Day 22:50+2 min+2 min
Mon 26 OctLe Day 22:490 min—
Thu 22 OctLe Day 22:480 min—
Wed 21 OctLe Day 22:49+1 min+1 min
Tue 20 OctLe Day 22:51+3 min+3 min
Mon 19 OctLe Day 22:50+2 min+2 min
Fri 16 OctLe Day 22:480 min—
Thu 15 OctLe Day 22:47−1 min—
Wed 14 OctLe Day 22:47−1 min—
Tue 13 OctLe Day 22:52+4 min+4 min
Mon 12 OctLe Day 22:47−1 min—
Fri 9 OctLe Day 22:490 min—
Thu 8 OctLe Day 22:49+1 min—
Wed 7 OctLe Day 22:47−1 min—
Tue 6 OctLe Day 22:470 min—
Mon 5 OctLe Day 22:490 min—
Tue 29 SeptLe Day 20:47+1 min—
Mon 28 SeptLe Day 20:46+1 min+7 min
Fri 11 SeptVallorbe 01:18+1 min+5 min
Sun 6 SeptLe Day 20:07−1 min—
Wed 19 AugLe Day 22:43−1 min—
Tue 18 AugLe Day 22:43−1 min+1 min
Thu 13 AugLe Day 23:430 min—