P28 18136 Vallorbe – Frasne

View line P28

Vallorbe 05:48 → Frasne 06:04 Mon, Tue, Wed, Thu, Fri 0 h 16 min · 2 stops SNCF

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 05:48 from Vallorbe · Wed 18 Nov

Next departure 05:48 today · Vallorbe
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 15 full · 0 partial · 0 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

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

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

Worst days

  • Wed 28 Oct Max en route +5 min · last fix heading to Frasne +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 75% W n=4
  • 100% T n=4
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 20 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:48on time on time
06:04on time on time

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
Tue 17 NovFrasne 06:040 min—
Mon 16 NovFrasne 06:040 min—
Fri 13 NovFrasne 06:040 min—
Thu 12 NovFrasne 06:040 min—
Wed 11 NovFrasne 06:040 min—
Tue 10 NovFrasne 06:040 min—
Mon 9 NovFrasne 06:040 min—
Thu 5 NovFrasne 06:040 min—
Wed 4 NovFrasne 06:040 min—
Tue 3 NovFrasne 06:040 min—
Fri 30 OctFrasne 06:050 min—
Thu 29 OctFrasne 06:050 min—
Wed 28 OctFrasne 06:05+5 min+5 min
Tue 27 OctFrasne 06:050 min—
Mon 26 OctFrasne 06:050 min—
Fri 9 OctFrasne 06:050 min—
Thu 8 OctFrasne 06:050 min—
Wed 7 OctFrasne 06:050 min—
Tue 6 OctFrasne 06:050 min—
Mon 5 OctStopPoint:OCETrain TE~dd472b30 06:060 min—