L52 867212 Dax – Pau

View line L52

Dax 09:54 → Pau 10:46 Mon, Tue, Wed, Thu, Fri 0 h 52 min · 5 stops SNCF

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 09:54 from Dax · Fri 13 Nov

Next departure 09:54 today · Dax
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 12 full · 0 partial · 1 no data
On-time · 90 days
88%
36/41 runs under 3 min
RT coverage: 41 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Pau, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 15 Sept Max en route +60 min · last fix heading to StopPoint:OCETrain TER-8767320 +60 min
  • Thu 1 Oct Max en route +60 min · last fix heading to StopPoint:OCETrain TER-8767227 +35 min
  • Wed 30 Sept Max en route +30 min · last fix heading to StopPoint:OCETrain TER-8767225 +30 min
  • Mon 14 Sept Max en route +20 min · last fix heading to StopPoint:OCETrain TER-8767200 +10 min
  • Mon 9 Nov Max en route +5 min · last fix heading to Pau +5 min

Distribution · 90 days

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

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

On-time by weekday

  • 78% M n=9
  • 89% T n=9
  • 88% W n=8
  • 86% T n=7
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 41 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
09:54on time on time
10:12 / 10:13≈ on time ≈ +3 min
10:22 / 10:23≈ on time ≈ +3 min
10:34 / 10:35≈ on time ≈ +4 min
10:46on 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

DateLast stopFinalMax
Thu 12 NovPau 10:470 min—
Tue 10 NovPau 10:470 min—
Mon 9 NovPau 10:52+5 min+5 min
Fri 6 NovPau 10:470 min—
Thu 5 NovPau 10:47No data—
Wed 4 NovPau 10:470 min—
Tue 3 NovPau 10:470 min—
Mon 2 NovPau 10:470 min—
Fri 30 OctPau 10:470 min—
Thu 29 OctPau 10:470 min—
Wed 28 OctPau 10:470 min—
Tue 27 OctPau 10:470 min—
Mon 26 OctPau 10:470 min—
Fri 9 OctPau 10:480 min+5 min
Thu 8 OctPau 10:470 min—
Wed 7 OctPau 10:470 min+5 min
Tue 6 OctPau 10:470 min—
Mon 5 OctStopPoint:OCETrain TE~99accf36 10:470 min+5 min
Fri 2 OctStopPoint:OCETrain TER-8767200 10:460 min+10 min
Thu 1 OctStopPoint:OCETrain TER-8767227 10:47+35 min+60 min
Wed 30 SeptStopPoint:OCETrain TER-8767225 10:47+30 min+30 min
Tue 29 SeptStopPoint:OCETrain TER-8767200 10:460 min—
Mon 28 SeptStopPoint:OCETrain TER-8767200 10:460 min—
Fri 25 SeptStopPoint:OCETrain TER-8767200 10:460 min—
Thu 24 SeptStopPoint:OCETrain TER-8767200 10:460 min—
Wed 23 SeptStopPoint:OCETrain TER-8767200 10:460 min—
Tue 22 SeptStopPoint:OCETrain TER-8767200 10:460 min+5 min
Mon 21 SeptStopPoint:OCETrain TER-8767200 10:460 min—
Fri 18 SeptStopPoint:OCETrain TER-8767200 10:470 min—
Thu 17 SeptStopPoint:OCETrain TER-8767200 10:46No data—