L52 867201 Pau – Dax

View line L52

Pau 05:02 → Dax 05:54 Mon, Tue, Wed, Thu, Fri 0 h 52 min · 5 stops SNCF

It does not run today

Last recorded run: Friday 13 November 0 min

Next service: Monday 05:02 from Pau · Mon 16 Nov

Next departure 05:02 Monday · Pau
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 14 full · 0 partial · 1 no data
On-time · 90 days
88%
38/43 runs under 3 min
RT coverage: 43 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Fri 21 Aug Max en route +100 min · last fix heading to StopPoint:OCETrain TER-8767320 +100 min
  • Thu 1 Oct Max en route +60 min · last fix heading to StopPoint:OCETrain TER-8758255 +60 min
  • Wed 4 Nov Max en route +25 min · last fix heading to Dax +25 min
  • Wed 9 Sept Max en route +20 min · last fix heading to StopPoint:OCETrain TER-8758175 +10 min
  • Thu 15 Oct Max en route +15 min · last fix heading to Bordeaux Saint-Jean +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 38
  • 3–10 min 2% · 1
  • 10–30 min 5% · 2
  • 30+ min 5% · 2

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 75% W n=8
  • 80% T n=10
  • 89% F n=9
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 stops).

Last 90 days, 43 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
05:02on time on time
05:14 / 05:15≈ on time ≈ +2 min
05:25 / 05:26≈ on time ≈ +3 min
05:36 / 05:37≈ on time ≈ +3 min
05:54on time +4 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 NovDax 05:540 min—
Thu 12 NovDax 05:540 min—
Tue 10 NovDax 05:540 min—
Thu 5 NovDax 05:54No data—
Wed 4 NovDax 06:19+25 min+25 min
Mon 2 NovDax 05:540 min—
Fri 30 OctDax 05:550 min—
Thu 29 OctDax 05:550 min—
Wed 28 OctDax 05:550 min—
Tue 27 OctDax 05:550 min—
Thu 22 OctDax 05:550 min—
Wed 21 OctDax 05:550 min—
Tue 20 OctDax 05:550 min—
Mon 19 OctDax 05:550 min—
Fri 16 OctBordeaux Saint-Jean 07:340 min—
Thu 15 OctBordeaux Saint-Jean 07:39+5 min+15 min
Wed 14 OctBordeaux Saint-Jean 07:330 min+5 min
Tue 13 OctBordeaux Saint-Jean 07:330 min+5 min
Mon 12 OctBordeaux Saint-Jean 07:330 min—
Fri 9 OctBordeaux Saint-Jean 07:340 min—
Thu 8 OctBordeaux Saint-Jean 07:330 min—
Wed 7 OctBordeaux Saint-Jean 07:340 min+5 min
Tue 6 OctBordeaux Saint-Jean 07:340 min—
Mon 5 OctStopPoint:OCETrain TE~5a4b4ef6 07:340 min—
Fri 2 OctStopPoint:OCETrain TER-8758100 07:310 min—
Thu 1 OctStopPoint:OCETrain TER-8758255 07:31+60 min+60 min
Wed 30 SeptStopPoint:OCETrain TER-8758100 07:310 min+5 min
Tue 29 SeptStopPoint:OCETrain TER-8758100 07:310 min—
Fri 11 SeptStopPoint:OCETrain TER-8758100 07:320 min—
Thu 10 SeptStopPoint:OCETrain TER-8758100 07:310 min—