F51 866529 Dax – Hendaye

View line F51

Dax 12:44 → Hendaye 14:09 Mon, Tue, Wed, Thu, Fri 1 h 25 min · 14 stops SNCF

Running now · updated 12:53

Position estimated from the timetable

Between Dax and Saubusse 0 min

Estimated arrival at Hendaye 14:09 · 38 km/h

  1. Dax12:44
  2. Saubusse12:53
  3. Saint-Geours12:57
  4. Bénesse-Maremne13:07
  5. Boucau13:23
  6. Biarritz13:40
  7. Hendaye14:09

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

On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 10 full · 1 partial · 1 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 18 full · 1 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

  • Mon 5 Oct Max en route +10 min · last fix heading to Hendaye +10 min
  • Thu 29 Oct Max en route +5 min · last fix heading to Hendaye +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=5
  • 100% W n=4
  • 67% T n=3
  • 100% 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, 19 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
12:44on time +1 minPassed
12:53 / 12:54≈ on time ≈ +2 minNext
12:57 / 12:58≈ on time ≈ +2 min
13:02 / 13:03≈ on time ≈ +2 min
13:07 / 13:08≈ on time ≈ +2 min
13:13 / 13:14≈ on time ≈ +2 min
13:16 / 13:17≈ on time ≈ +2 min
13:23 / 13:24≈ on time ≈ +2 min
13:29 / 13:32≈ on time ≈ +2 min
13:40 / 13:41≈ on time ≈ +2 min
13:46 / 13:47≈ on time ≈ +2 min
13:55 / 13:56≈ on time ≈ +2 min
14:05 / 14:06≈ on time ≈ +2 min
14:09on time +2 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 NovSaubusse 12:49Partial coverage0 min—
Tue 10 NovHendaye 14:090 min—
Mon 9 NovHendaye 14:090 min—
Fri 6 NovHendaye 14:090 min—
Thu 5 NovHendaye 14:09No data—
Wed 4 NovHendaye 14:090 min—
Tue 3 NovHendaye 14:090 min—
Fri 30 OctHendaye 14:100 min—
Thu 29 OctHendaye 14:15+5 min+5 min
Wed 28 OctHendaye 14:100 min—
Tue 27 OctHendaye 14:100 min—
Mon 26 OctHendaye 14:110 min—
Fri 9 OctHendaye 14:100 min—
Thu 8 OctHendaye 14:100 min—
Wed 7 OctHendaye 14:100 min+5 min
Tue 6 OctHendaye 14:100 min—
Mon 5 OctHendaye 14:20+10 min+10 min
Thu 10 SeptStopPoint:OCETrain TER-8767700 14:080 min—
Wed 2 SeptStopPoint:OCETrain TER-8767700 14:090 min—
Tue 1 SeptStopPoint:OCETrain TER-8767700 14:080 min—