P18 895701 Frasne – Pontarlier

View line P18

Frasne 07:17 → Pontarlier 07:33 Mon, Tue, Wed, Thu, Fri, Sat 0 h 16 min · 4 stops SNCF

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 07:17 from Frasne · Thu 5 Nov

Next departure 07:17 today · Frasne
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 24 full · 0 partial · 0 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 26 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 Pontarlier, in minutes. One bar per run.

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

Worst days

  • Sat 31 Oct Max en route +5 min · last fix heading to Pontarlier +5 min
  • Thu 22 Oct Max en route +5 min · last fix heading to Pontarlier +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 24
  • 3–10 min 8% · 2
  • 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
  • 75% T n=4
  • 100% F n=4
  • 75% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 26 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
07:17on time on time
07:20 / 07:21≈ on time ≈ on time
07:25 / 07:26≈ on time ≈ on time
07:33on 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
Wed 4 NovPontarlier 07:340 min—
Tue 3 NovPontarlier 07:340 min—
Sat 31 OctPontarlier 07:44+5 min+5 min
Fri 30 OctPontarlier 07:340 min—
Thu 29 OctPontarlier 07:340 min—
Wed 28 OctPontarlier 07:340 min—
Tue 27 OctPontarlier 07:340 min—
Mon 26 OctPontarlier 07:340 min—
Sat 24 OctPontarlier 07:390 min—
Fri 23 OctPontarlier 07:340 min—
Thu 22 OctPontarlier 07:39+5 min+5 min
Wed 21 OctPontarlier 07:340 min—
Tue 20 OctPontarlier 07:340 min—
Mon 19 OctPontarlier 07:340 min—
Sat 17 OctPontarlier 07:390 min—
Fri 16 OctPontarlier 07:350 min—
Thu 15 OctPontarlier 07:350 min—
Wed 14 OctPontarlier 07:340 min—
Tue 13 OctPontarlier 07:340 min—
Mon 12 OctPontarlier 07:340 min—
Sat 10 OctPontarlier 07:390 min—
Fri 9 OctPontarlier 07:350 min—
Thu 8 OctPontarlier 07:340 min—
Wed 7 OctPontarlier 07:350 min—
Tue 6 OctPontarlier 07:350 min—
Mon 5 OctStopPoint:OCETrain TE~fedb6afd 07:350 min—