L52 867250 Dax – Pau

View line L52

Dax 16:50 → Pau 17:43 Mon, Tue, Wed, Thu 0 h 53 min · 5 stops SNCF

It does not run today

Last recorded run: Thursday 12 November +5 min

Next service: Monday 16:50 from Dax · Mon 16 Nov

Next departure 16:50 Monday · Dax
On-time · 30 days
71%
10/14 runs under 3 min
RT coverage: 14 full · 0 partial · 0 no data
On-time · 90 days
84%
42/50 runs under 3 min
RT coverage: 50 full · 0 partial · 0 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: +5 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 5 Nov Max en route +15 min · last fix heading to Pau +10 min
  • Thu 12 Nov Max en route +5 min · last fix heading to Pau +5 min
  • Thu 29 Oct Max en route +5 min · last fix heading to Pau +5 min
  • Thu 22 Oct Max en route +5 min · last fix heading to Pau +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 42
  • 3–10 min 12% · 6
  • 10–30 min 2% · 1
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=12
  • 92% T n=13
  • 83% W n=12
  • 62% T n=13
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 50 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
16:50on time +5 min
17:07 / 17:08≈ on time ≈ +5 min
17:18 / 17:19≈ on time ≈ +5 min
17:31 / 17:32≈ on time ≈ +5 min
17:43on 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 17:49+5 min+5 min
Tue 10 NovPau 17:440 min—
Mon 9 NovPau 17:440 min—
Thu 5 NovPau 17:54+10 min+15 min
Wed 4 NovPau 17:440 min—
Tue 3 NovPau 17:450 min—
Thu 29 OctPau 17:49+5 min+5 min
Wed 28 OctPau 17:440 min—
Tue 27 OctPau 17:440 min—
Mon 26 OctPau 17:450 min—
Thu 22 OctPau 17:50+5 min+5 min
Wed 21 OctPau 17:450 min—
Tue 20 OctPau 17:440 min—
Mon 19 OctPau 17:440 min—
Thu 15 OctPau 17:45+5 min+5 min
Wed 14 OctPau 17:49+5 min+10 min
Tue 13 OctPau 17:440 min—
Mon 12 OctPau 17:440 min—
Thu 8 OctPau 17:450 min—
Wed 7 OctPau 17:440 min—
Tue 6 OctPau 17:440 min—
Mon 5 OctPau 17:440 min—
Thu 1 OctStopPoint:OCETrain TER-8767200 17:430 min+30 min
Wed 30 SeptStopPoint:OCETrain TER-8767200 17:420 min—
Tue 29 SeptStopPoint:OCETrain TER-8767200 17:420 min—
Mon 28 SeptStopPoint:OCETrain TER-8767200 17:420 min—
Thu 24 SeptStopPoint:OCETrain TER-8767200 17:420 min—
Wed 23 SeptStopPoint:OCETrain TER-8767200 17:420 min—
Tue 22 SeptStopPoint:OCETrain TER-8767200 17:420 min—
Mon 21 SeptStopPoint:OCETrain TER-8767200 17:420 min—