L52 867245 Pau – Dax

View line L52

Pau 11:15 → Dax 12:08 Wed, Sat, Sun 0 h 53 min · 5 stops SNCF

✓ Today’s run finished

Today it reached Dax at 12:08 0 min

  1. Pau11:15
  2. Artix11:27
  3. Orthez11:38
  4. Puyoô11:49
  5. Dax12:08

Next service: tomorrow 11:15 from Pau · Sun 15 Nov

Next departure 11:15 tomorrow · Pau
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 16 full · 0 partial · 0 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: +2 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

  • Sat 24 Oct Max en route +20 min · last fix heading to Dax +20 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 0% · 0
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • 100% W n=1
  • — T n=0
  • — F n=0
  • 89% S n=9
  • 100% S n=6

Stops and timetable

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

Last 90 days, 16 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
11:15on time +5 min
11:27 / 11:28≈ on time ≈ +4 min
11:38 / 11:39≈ on time ≈ +3 min
11:49 / 11:50≈ on time ≈ +2 min
12:08on 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
Sat 14 NovDax 12:090 min—
Wed 11 NovDax 12:090 min—
Sun 8 NovDax 12:090 min—
Sat 7 NovDax 12:090 min—
Sun 1 NovDax 12:090 min—
Sat 31 OctDax 12:090 min—
Sun 25 OctDax 12:090 min—
Sat 24 OctDax 12:29+20 min+20 min
Sun 18 OctDax 12:090 min—
Sat 17 OctDax 12:090 min—
Sun 11 OctDax 12:090 min—
Sat 10 OctDax 12:090 min—
Sun 4 OctStopPoint:OCETrain TE~90c4967a 12:090 min—
Sat 26 SeptStopPoint:OCETrain TER-8767320 12:000 min—
Sat 19 SeptStopPoint:OCETrain TER-8767320 12:000 min—
Sat 12 SeptStopPoint:OCETrain TER-8767320 12:000 min+10 min