L52 867257 Pau – Dax

View line L52

Pau 16:25 → Dax 17:18 Mon, Tue, Wed, Thu, Fri 0 h 53 min · 5 stops SNCF

✓ Today’s run finished

Today, last fix heading to Dax at 17:19 No data

  1. Pau16:25
  2. Artix16:37
  3. Orthez16:48
  4. Puyoô16:59
  5. Dax17:18

Next service: tomorrow 16:25 from Pau · Fri 6 Nov

Next departure 16:25 tomorrow · Pau
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 1 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 Dax, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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:25on time on time
16:37 / 16:38≈ on time ≈ on time
16:48 / 16:49≈ on time ≈ on time
16:59 / 17:00≈ on time ≈ on time
17:18on 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 5 NovDax 17:19No data—
Wed 4 NovDax 17:190 min—
Tue 3 NovDax 17:200 min—
Fri 30 OctDax 17:190 min—
Thu 29 OctDax 17:190 min—
Wed 28 OctDax 17:190 min—
Tue 27 OctDax 17:190 min—
Mon 26 OctDax 17:200 min—
Fri 23 OctDax 17:160 min—
Thu 22 OctDax 17:200 min—
Wed 21 OctDax 17:190 min—
Tue 20 OctDax 17:190 min—
Mon 19 OctDax 17:200 min—
Fri 16 OctDax 17:190 min—
Thu 15 OctDax 17:190 min—
Wed 14 OctDax 17:190 min—
Mon 12 OctDax 17:190 min—
Fri 9 OctDax 17:190 min—
Thu 8 OctDax 17:190 min—
Wed 7 OctDax 17:190 min—
Tue 6 OctDax 17:190 min—
Mon 5 OctDax 17:190 min—
Fri 2 OctStopPoint:OCETrain TER-8767320 17:170 min—
Fri 25 SeptStopPoint:OCETrain TER-8767320 17:170 min—