F51 866520 Hendaye – Dax

View line F51

Hendaye 15:50 → Dax 17:13 Mon, Tue, Wed, Thu, Fri 1 h 23 min · 14 stops SNCF

Running now · updated 16:40

Position estimated from the timetable

Between Labenne and Bénesse-Maremne 0 min

Estimated arrival at Dax 17:13 · 101 km/h

  1. Hendaye15:50
  2. Saint-Jean-de-Luz - Ciboure16:01
  3. Biarritz16:13
  4. Ondres16:35
  5. Labenne16:39
  6. Bénesse-Maremne16:44
  7. Dax17:13

Today it is running no worse than usual: typical arrival delay is 0 min; 73% of the last 15 runs arrived on time.

On-time · 30 days
73%
11/15 runs under 3 min
RT coverage: 14 full · 1 partial · 1 no data
On-time · 90 days
83%
19/23 runs under 3 min
RT coverage: 22 full · 1 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

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

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

Worst days

  • Thu 12 Nov Max en route +5 min · last fix heading to Dax +5 min
  • Fri 30 Oct Max en route +5 min · last fix heading to Dax +5 min
  • Wed 28 Oct Max en route +5 min · last fix heading to Dax +5 min
  • Mon 26 Oct Max en route +5 min · last fix heading to Dax +5 min

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 83% · 19
  • 3–10 min 17% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (14 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 10Today
15:50on time on timePassed
15:53 / 15:54≈ on time ≈ on timePassed
16:01 / 16:02≈ on time ≈ +1 minPassed
16:07 / 16:08≈ on time ≈ +1 minPassed
16:13 / 16:14≈ on time ≈ +1 minPassed
16:25 / 16:27≈ on time ≈ +2 minPassed
16:30 / 16:31≈ on time ≈ +2 minPassed
16:35 / 16:36≈ on time ≈ +3 minPassed
16:39 / 16:40≈ on time ≈ +3 minPassed
16:44 / 16:45≈ on time ≈ +3 minNext
16:49 / 16:50≈ on time ≈ +4 min
16:54 / 16:55≈ on time ≈ +4 min
16:59 / 17:00≈ on time ≈ +4 min
17:13on time +5 min

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 13 NovLabenne 16:40Partial coverage0 min—
Thu 12 NovDax 17:19+5 min+5 min
Tue 10 NovDax 17:140 min—
Mon 9 NovDax 17:140 min—
Fri 6 NovDax 17:140 min—
Thu 5 NovDax 17:14No data—
Wed 4 NovDax 17:140 min—
Tue 3 NovDax 17:150 min—
Fri 30 OctDax 17:19+5 min+5 min
Wed 28 OctDax 17:19+5 min+5 min
Mon 26 OctDax 17:20+5 min+5 min
Thu 22 OctDax 17:150 min+5 min
Wed 21 OctDax 17:140 min—
Tue 20 OctDax 17:140 min—
Mon 19 OctDax 17:150 min—
Thu 15 OctDax 17:140 min—
Wed 14 OctDax 17:140 min—
Tue 13 OctDax 17:140 min—
Mon 12 OctDax 17:140 min—
Fri 9 OctDax 17:140 min—
Thu 8 OctDax 17:140 min—
Wed 7 OctDax 17:140 min—
Tue 6 OctDax 17:140 min—
Mon 5 OctDax 17:150 min—