F51 866537 Dax – Hendaye

View line F51

Dax 17:10 → Hendaye 18:34 Mon, Tue, Wed, Thu, Fri 1 h 24 min · 14 stops SNCF

It has not run yet today

Last recorded run: Tuesday 3 November 0 min

Next service: today 17:10 from Dax · Thu 5 Nov

Next departure 17:10 today · Dax
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 16 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: +3 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

  • Wed 28 Oct Max en route +5 min · last fix heading to Hendaye +5 min
  • Fri 23 Oct Max en route +5 min · last fix heading to Hendaye +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=7
  • 86% W n=7
  • 100% T n=3
  • 80% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (14 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
17:10on time on time
17:19 / 17:20≈ on time ≈ on time
17:23 / 17:24≈ on time ≈ on time
17:28 / 17:29≈ on time ≈ on time
17:33 / 17:34≈ on time ≈ on time
17:38 / 17:39≈ on time ≈ on time
17:42 / 17:43≈ on time ≈ on time
17:49 / 17:50≈ on time ≈ on time
17:54 / 17:56≈ on time ≈ on time
18:04 / 18:05≈ on time ≈ on time
18:10 / 18:11≈ on time ≈ on time
18:19 / 18:20≈ on time ≈ on time
18:29 / 18:30≈ on time ≈ on time
18:34on 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
Tue 3 NovHendaye 18:340 min—
Fri 30 OctHendaye 18:350 min—
Thu 29 OctHendaye 18:350 min—
Wed 28 OctHendaye 18:40+5 min+5 min
Tue 27 OctHendaye 18:350 min—
Mon 26 OctHendaye 18:360 min—
Fri 23 OctHendaye 18:41+5 min+5 min
Wed 21 OctHendaye 18:360 min—
Tue 20 OctHendaye 18:350 min—
Mon 19 OctHendaye 18:350 min—
Fri 16 OctHendaye 18:350 min—
Wed 14 OctHendaye 18:350 min—
Mon 12 OctHendaye 18:350 min—
Fri 9 OctHendaye 18:350 min—
Thu 8 OctHendaye 18:360 min—
Wed 7 OctHendaye 18:350 min—
Tue 6 OctHendaye 18:350 min—
Mon 5 OctHendaye 18:350 min—
Fri 25 SeptStopPoint:OCETrain TER-8767700 18:330 min—
Thu 10 SeptStopPoint:OCETrain TER-8767700 18:340 min—
Wed 2 SeptStopPoint:OCETrain TER-8767700 18:340 min+10 min
Tue 1 SeptStopPoint:OCETrain TER-8767700 18:330 min—
Tue 25 AugStopPoint:OCETrain TER-8767700 18:340 min+5 min
Wed 19 AugStopPoint:OCETrain TER-8767700 18:330 min—
Wed 12 AugStopPoint:OCETrain TER-8767700 18:330 min—
Tue 11 AugStopPoint:OCETrain TER-8767700 18:330 min—