L52 867252 Dax – Pau

View line L52

Dax 18:04 → Pau 18:59 Mon, Tue, Wed, Thu, Fri 0 h 55 min · 5 stops SNCF

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 18:04 from Dax · Fri 13 Nov

Next departure 18:04 today · Dax
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 1 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 33 full · 0 partial · 2 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: 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 33
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 33 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
18:04on time on time
18:21 / 18:22≈ on time ≈ on time
18:32 / 18:33≈ on time ≈ on time
18:44 / 18:45≈ on time ≈ on time
18:59on 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
Thu 12 NovPau 18:590 min—
Tue 10 NovPau 18:590 min—
Mon 9 NovPau 18:590 min—
Fri 6 NovPau 19:040 min—
Thu 5 NovPau 18:59No data—
Wed 4 NovPau 18:590 min—
Tue 3 NovPau 19:000 min—
Fri 30 OctPau 19:040 min—
Thu 29 OctPau 19:000 min—
Wed 28 OctPau 19:000 min—
Tue 27 OctPau 19:000 min—
Mon 26 OctPau 19:010 min+5 min
Fri 23 OctPau 19:050 min—
Thu 22 OctPau 19:010 min—
Wed 21 OctPau 19:000 min—
Tue 20 OctPau 19:000 min—
Fri 16 OctPau 19:040 min—
Thu 15 OctPau 19:000 min—
Wed 14 OctPau 19:000 min—
Tue 13 OctArtix 18:40Partial coverageNo data—
Mon 12 OctPau 19:000 min—
Fri 9 OctPau 19:040 min—
Thu 8 OctPau 19:000 min—
Wed 7 OctPau 19:000 min—
Tue 6 OctPau 19:000 min—
Mon 5 OctPau 19:000 min—
Mon 31 AugStopPoint:OCETrain TER-8767200 18:580 min—
Thu 27 AugStopPoint:OCETrain TER-8767200 18:580 min—
Wed 26 AugStopPoint:OCETrain TER-8767200 18:580 min+5 min
Tue 25 AugStopPoint:OCETrain TER-8767200 18:590 min—