P28 18146 Pontarlier – Vallorbe

View line P28

Pontarlier 17:34 → Vallorbe 18:11 Mon, Tue, Wed, Thu, Fri 0 h 37 min · 5 stops SNCF

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: tomorrow 17:34 from Pontarlier · Mon 9 Nov

Next departure 17:34 tomorrow · Pontarlier
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
17:34on time on time
17:39 / 17:40≈ on time ≈ on time
17:45 / 17:46≈ on time ≈ on time
17:51 / 17:55≈ on time ≈ on time
18:11on 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 6 NovVallorbe 18:120 min—
Thu 5 NovVallorbe 18:12No data—
Wed 4 NovVallorbe 18:120 min—
Tue 3 NovVallorbe 18:130 min—
Mon 2 NovVallorbe 18:120 min—
Fri 30 OctVallorbe 18:120 min—
Thu 29 OctVallorbe 18:120 min—
Wed 28 OctVallorbe 18:120 min—
Tue 27 OctVallorbe 18:120 min—
Mon 26 OctVallorbe 18:130 min—
Fri 23 OctFrasne 17:530 min—
Thu 22 OctFrasne 17:530 min—
Wed 21 OctFrasne 17:530 min—
Tue 20 OctFrasne 17:520 min—
Mon 19 OctFrasne 17:520 min—
Fri 16 OctFrasne 17:520 min—
Thu 15 OctFrasne 17:520 min—
Wed 14 OctFrasne 17:520 min—
Tue 13 OctFrasne 17:520 min—
Mon 12 OctFrasne 17:520 min—
Fri 9 OctVallorbe 18:120 min—
Thu 8 OctVallorbe 18:130 min—
Wed 7 OctVallorbe 18:120 min—
Tue 6 OctVallorbe 18:120 min—
Mon 5 OctVallorbe 18:120 min—
Tue 25 AugStopPoint:OCETrain TER-8501103 18:110 min—
Wed 19 AugStopPoint:OCETrain TER-8501103 18:100 min—
Wed 12 AugStopPoint:OCETrain TER-8501103 18:100 min—
Tue 11 AugStopPoint:OCETrain TER-8501103 18:100 min—