L52 867256 Dax – Pau

View line L52

Dax 20:22 → Pau 21:14 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 20:22 from Dax · Fri 13 Nov

Next departure 20:22 today · Dax
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 17 full · 0 partial · 1 no data
On-time · 90 days
82%
31/38 runs under 3 min
RT coverage: 38 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+12min
9 in 10 runs arrive with less than this
30 days: +10 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

  • Mon 2 Nov Max en route +50 min · last fix heading to Pau +50 min
  • Fri 23 Oct Max en route +25 min · last fix heading to Pau +25 min
  • Thu 17 Sept Max en route +15 min · last fix heading to StopPoint:OCETrain TER-8767200 +15 min
  • Thu 3 Sept Max en route +15 min · last fix heading to StopPoint:OCETrain TER-8767221 +15 min
  • Wed 16 Sept Max en route +15 min · last fix heading to StopPoint:OCETrain TER-8767200 +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 31
  • 3–10 min 5% · 2
  • 10–30 min 11% · 4
  • 30+ min 3% · 1

On-time by weekday

  • 80% M n=5
  • 82% T n=11
  • 88% W n=8
  • 78% T n=9
  • 80% 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, 38 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
20:22on time +15 min
20:39 / 20:40≈ on time ≈ +11 min
20:50 / 20:51≈ on time ≈ +9 min
21:01 / 21:02≈ on time ≈ +11 min
21:14on time +12 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 21:140 min—
Tue 10 NovPau 21:140 min—
Mon 9 NovPau 21:140 min—
Fri 6 NovPau 21:140 min—
Thu 5 NovPau 21:14No data—
Tue 3 NovPau 21:140 min—
Mon 2 NovPau 21:59+50 min+50 min
Fri 30 OctPau 21:150 min—
Thu 29 OctPau 21:150 min—
Wed 28 OctPau 21:150 min—
Tue 27 OctPau 21:150 min—
Mon 26 OctPau 21:160 min—
Fri 23 OctPau 21:41+25 min+25 min
Thu 22 OctPau 21:150 min—
Wed 21 OctPau 21:150 min—
Tue 20 OctPau 21:150 min—
Fri 16 OctPau 21:150 min—
Thu 15 OctPau 21:150 min—
Wed 14 OctPau 21:150 min—
Tue 13 OctPau 21:20+5 min+10 min
Mon 12 OctPau 21:150 min—
Fri 9 OctPau 21:150 min—
Thu 8 OctPau 21:130 min—
Wed 7 OctPau 21:150 min—
Tue 6 OctPau 21:20+5 min+10 min
Mon 5 OctPau 21:150 min—
Tue 29 SeptStopPoint:OCETrain TER-8767200 21:130 min+35 min
Thu 24 SeptStopPoint:OCETrain TER-8767200 21:140 min+15 min
Wed 23 SeptStopPoint:OCETrain TER-8767200 21:130 min+15 min
Tue 22 SeptStopPoint:OCETrain TER-8767200 21:130 min+15 min