P28 18133 Frasne → Vallorbe

View line P28

Frasne 06:18 → Vallorbe 06:37 Mon, Tue, Wed, Thu, Fri 0 h 19 min · 3 stops SNCF

TER 18133 Frasne–Vallorbe: final delay under 3 min on 18 of its 18 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 23 Nov 2026, 00:22 (GMT+1).

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 06:18 from Frasne · Mon 23 Nov

Next departure 06:18 today · Frasne
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 18 full · 0 partial · 0 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 23 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 Vallorbe, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
06:18on time on time
06:27 / 06:28≈ on time ≈ on time
06:37on 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
Fri 20 NovVallorbe 06:390 min—
Thu 19 NovVallorbe 06:380 min—
Wed 18 NovVallorbe 06:380 min—
Tue 17 NovVallorbe 06:380 min—
Mon 16 NovVallorbe 06:380 min—
Fri 13 NovVallorbe 06:380 min—
Thu 12 NovVallorbe 06:380 min—
Wed 11 NovVallorbe 06:380 min—
Tue 10 NovVallorbe 06:380 min—
Mon 9 NovVallorbe 06:380 min—
Thu 5 NovVallorbe 06:380 min—
Wed 4 NovVallorbe 06:380 min—
Tue 3 NovVallorbe 06:380 min—
Fri 30 OctVallorbe 06:380 min—
Thu 29 OctVallorbe 06:380 min—
Wed 28 OctVallorbe 06:380 min—
Tue 27 OctVallorbe 06:380 min—
Mon 26 OctVallorbe 06:380 min—
Fri 9 OctVallorbe 06:380 min—
Thu 8 OctVallorbe 06:390 min—
Wed 7 OctVallorbe 06:380 min—
Tue 6 OctVallorbe 06:380 min—
Mon 5 OctStopPoint:OCETrain TE~c045a2e7 06:390 min—