F51 866522 Hendaye – Dax
Alerts for train 866522
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line F51.
It has not run yet today
Last recorded run: Tuesday 10 November 0 min
Next service: today 16:26 from Hendaye · Fri 13 Nov
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
- Mon 26 Oct Max en route +15 min · last fix heading to Dax +15 min
- Tue 3 Nov 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
Distribution · 90 days
22 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 86% · 19
- 3–10 min 9% · 2
- 10–30 min 5% · 1
- 30+ min 0% · 0
On-time by weekday
- 83% M n=6
- 83% T n=6
- 67% W n=3
- 100% T n=4
- 100% F n=3
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 stops).
Last 90 days, 22 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 16:26 | on time | on time | |
| 16:30 / 16:31 | ≈ on time | ≈ on time | |
| 16:38 / 16:39 | ≈ on time | ≈ +1 min | |
| 16:43 / 16:44 | ≈ on time | ≈ +1 min | |
| 16:49 / 16:50 | ≈ on time | ≈ +1 min | |
| 17:01 / 17:03 | ≈ on time | ≈ +2 min | |
| 17:07 / 17:08 | ≈ on time | ≈ +2 min | |
| 17:12 / 17:13 | ≈ on time | ≈ +3 min | |
| 17:15 / 17:16 | ≈ on time | ≈ +3 min | |
| 17:20 / 17:21 | ≈ on time | ≈ +3 min | |
| 17:25 / 17:26 | ≈ on time | ≈ +4 min | |
| 17:31 / 17:32 | ≈ on time | ≈ +4 min | |
| 17:35 / 17:36 | ≈ on time | ≈ +4 min | |
| 17:49 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Tue 10 Nov | Dax 17:49 | 0 min | — |
| Mon 9 Nov | Dax 17:49 | 0 min | — |
| Fri 6 Nov | Dax 17:49 | 0 min | — |
| Thu 5 Nov | Dax 17:49 | 0 min | — |
| Tue 3 Nov | Dax 17:55 | +5 min | +5 min |
| Mon 2 Nov | Dax 17:49 | 0 min | — |
| Thu 29 Oct | Dax 17:50 | 0 min | — |
| Wed 28 Oct | Dax 17:55 | +5 min | +5 min |
| Tue 27 Oct | Dax 17:50 | 0 min | — |
| Mon 26 Oct | Dax 18:06 | +15 min | +15 min |
| Wed 21 Oct | Les Deux Jumeaux 16:27Partial coverage | 0 min | — |
| Tue 20 Oct | Dax 17:50 | 0 min | — |
| Mon 19 Oct | Dax 17:50 | 0 min | — |
| Fri 16 Oct | Dax 17:50 | 0 min | — |
| Thu 15 Oct | Dax 17:50 | 0 min | — |
| Tue 13 Oct | Dax 17:50 | 0 min | — |
| Mon 12 Oct | Dax 17:50 | 0 min | — |
| Fri 9 Oct | Dax 17:50 | 0 min | — |
| Thu 8 Oct | Dax 17:51 | 0 min | +5 min |
| Wed 7 Oct | Dax 17:50 | 0 min | — |
| Tue 6 Oct | Dax 17:50 | 0 min | +5 min |
| Mon 5 Oct | Dax 17:50 | 0 min | — |