D52 867241 Pau – Dax

View line D52

Pau 08:24 → Dax 09:17 Mon, Tue, Wed, Thu, Fri 0 h 53 min · 5 stops SNCF

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 08:24 from Pau · Thu 5 Nov

Next departure 08:24 today · Pau
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 22 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: +1 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 22 Oct Max en route +10 min · last fix heading to Dax +5 min
  • Thu 15 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 91% · 20
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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.

StopSched.Usually 9 days in 10
08:24on time on time
08:36 / 08:37≈ on time ≈ on time
08:47 / 08:48≈ on time ≈ on time
08:58 / 08:59≈ on time ≈ on time
09:17on 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 4 NovDax 09:180 min—
Tue 3 NovDax 09:190 min—
Mon 2 NovDax 09:180 min—
Fri 30 OctDax 09:180 min—
Thu 29 OctDax 09:180 min—
Wed 28 OctDax 09:180 min—
Tue 27 OctDax 09:180 min—
Mon 26 OctDax 09:180 min—
Fri 23 OctDax 09:180 min—
Thu 22 OctDax 09:23+5 min+10 min
Wed 21 OctDax 09:180 min—
Tue 20 OctDax 09:180 min—
Mon 19 OctDax 09:180 min—
Fri 16 OctDax 09:180 min—
Thu 15 OctDax 09:23+5 min+5 min
Wed 14 OctDax 09:180 min—
Mon 12 OctDax 09:190 min—
Fri 9 OctDax 09:190 min—
Thu 8 OctDax 09:180 min—
Wed 7 OctDax 09:190 min—
Tue 6 OctDax 09:180 min—
Mon 5 OctStopPoint:OCETrain TE~90c4967a 09:190 min—