F51 866533 Dax – Hendaye

View line F51

Dax 14:44 → Hendaye 16:08 Wed, Sat, Sun 1 h 24 min · 14 stops SNCF

It does not run today

Last recorded run: Wednesday 11 November 0 min

Next service: tomorrow 14:44 from Dax · Sat 14 Nov

Next departure 14:44 tomorrow · Dax
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 8 full · 0 partial · 0 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 21 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 Hendaye, in minutes. One bar per run.

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

Worst days

  • Sun 11 Oct Max en route +15 min · last fix heading to Hendaye +10 min
  • Wed 23 Sept Max en route +5 min · last fix heading to StopPoint:OCETrain TER-8767700 +5 min

Distribution · 90 days

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • 80% W n=5
  • — T n=0
  • — F n=0
  • 100% S n=6
  • 90% S n=10

Stops and timetable

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

Last 90 days, 21 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
14:44on time on time
14:53 / 14:54≈ on time ≈ on time
14:57 / 14:58≈ on time ≈ on time
15:02 / 15:03≈ on time ≈ on time
15:07 / 15:08≈ on time ≈ on time
15:13 / 15:14≈ on time ≈ on time
15:16 / 15:17≈ on time ≈ on time
15:23 / 15:24≈ on time ≈ on time
15:28 / 15:30≈ on time ≈ on time
15:38 / 15:39≈ on time ≈ on time
15:44 / 15:45≈ on time ≈ on time
15:54 / 15:55≈ on time ≈ on time
16:04 / 16:05≈ on time ≈ on time
16:08on 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 11 NovHendaye 16:090 min—
Sun 8 NovHendaye 16:090 min—
Sun 1 NovHendaye 16:090 min—
Sat 31 OctHendaye 16:100 min—
Sun 25 OctHendaye 16:090 min—
Sat 24 OctHendaye 16:090 min—
Sun 18 OctHendaye 16:090 min—
Sat 17 OctHendaye 16:090 min—
Sun 11 OctHendaye 16:19+10 min+15 min
Sat 10 OctHendaye 16:100 min—
Sun 4 OctStopPoint:OCETrain TE~aa035970 16:090 min—
Sat 3 OctStopPoint:OCETrain TER-8767700 16:070 min—
Wed 30 SeptStopPoint:OCETrain TER-8767700 16:070 min—
Sun 27 SeptStopPoint:OCETrain TER-8767700 16:070 min—
Wed 23 SeptStopPoint:OCETrain TER-8767700 16:07+5 min+5 min
Sun 20 SeptStopPoint:OCETrain TER-8767700 16:080 min—
Sat 19 SeptStopPoint:OCETrain TER-8767700 16:070 min+5 min
Wed 16 SeptStopPoint:OCETrain TER-8767700 16:070 min—
Sun 13 SeptStopPoint:OCETrain TER-8767700 16:070 min—
Wed 9 SeptStopPoint:OCETrain TER-8767700 16:070 min—
Sun 6 SeptStopPoint:OCETrain TER-8767700 16:070 min—