R4 14497 Vallorbe – Le Day

View line R4

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

It does not run today

Last recorded run: Friday 13 November +2 min

Next service: Monday 23:42 from Vallorbe · Mon 16 Nov

Next departure 23:42 Monday · Vallorbe
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
95%
37/39 runs under 3 min
RT coverage: 39 full · 0 partial · 2 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

  • Mon 9 Nov Max en route +4 min · last fix heading to Le Day +4 min
  • Tue 10 Nov Max en route +3 min · last fix heading to Le Day +3 min

Distribution · 90 days

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

  • Early 15% · 6
  • On time 79% · 31
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 83% T n=6
  • 100% W n=7
  • 100% T n=6
  • 100% F n=12
  • 100% S n=2
  • — S n=0

Stops and timetable

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

Last 90 days, 39 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
23:42+1 min +1 min
23: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
Fri 13 NovLe Day 23:49+2 min+2 min
Thu 12 NovLe Day 23:50+2 min+2 min
Wed 11 NovLe Day 23:480 min—
Tue 10 NovLe Day 23:49+3 min+3 min
Mon 9 NovLe Day 23:53+4 min+4 min
Fri 6 NovLe Day 23:480 min—
Thu 5 NovLe Day 23:47−1 min—
Wed 4 NovLe Day 23:47−1 min—
Tue 3 NovLe Day 23:47−1 min—
Mon 2 NovLe Day 23:49+1 min—
Fri 30 OctLe Day 23:480 min—
Thu 29 OctLe Day 23:47−1 min—
Wed 28 OctLe Day 23:49+1 min—
Tue 27 OctLe Day 23:480 min—
Mon 26 OctLe Day 23:48−1 min—
Fri 23 OctLe Day 23:47−1 min—
Thu 22 OctLe Day 23:49+1 min+1 min
Wed 21 OctLe Day 23:47−1 min—
Tue 20 OctLe Day 23:480 min—
Mon 19 OctLe Day 23:480 min—
Fri 16 OctLe Day 23:480 min—
Thu 15 OctLe Day 23:49+1 min—
Wed 14 OctLe Day 23:47−1 min—
Tue 13 OctLe Day 23:490 min—
Mon 12 OctLe Day 23:47−1 min—
Fri 9 OctLe Day 23:49+1 min—
Thu 8 OctLe Day 23:480 min—
Wed 7 OctLe Day 23:48−1 min—
Tue 6 OctLe Day 23:480 min—
Mon 5 OctLe Day 23:480 min—