F41+ 866238 Arcachon – Libourne

View line F41+

Arcachon 14:02 → Libourne 15:34 Daily 1 h 32 min · 19 stops SNCF

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 14:02 from Arcachon · Thu 5 Nov

Next departure 14:02 today · Arcachon
On-time · 30 days
83%
24/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
83%
70/84 runs under 3 min
RT coverage: 84 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 Libourne, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 18 Sept Max en route +25 min · last fix heading to StopPoint:OCETrain TER-8758475 +25 min
  • Sun 9 Aug Max en route +20 min · last fix heading to StopPoint:OCETrain TER-8758471 +10 min
  • Fri 30 Oct Max en route +5 min · last fix heading to Libourne +5 min
  • Wed 28 Oct Max en route +5 min · last fix heading to Libourne +5 min
  • Tue 27 Oct Max en route +5 min · last fix heading to Libourne +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 70
  • 3–10 min 14% · 12
  • 10–30 min 2% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=13
  • 85% T n=13
  • 77% W n=13
  • 92% T n=12
  • 83% F n=12
  • 85% S n=13
  • 63% S n=8

Stops and timetable

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

Last 90 days, 84 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
14:02on time on time
14:06 / 14:07≈ on time ≈ on time
14:09≈ on time ≈ on time
14:13 / 14:14≈ on time ≈ +1 min
14:18 / 14:19≈ on time ≈ +1 min
14:24 / 14:25≈ on time ≈ +1 min
14:32 / 14:33≈ on time ≈ +2 min
14:41 / 14:42≈ on time ≈ +2 min
14:45 / 14:46≈ on time ≈ +2 min
14:49 / 14:50≈ on time ≈ +3 min
14:52 / 14:53≈ on time ≈ +3 min
14:58 / 15:02≈ on time ≈ +3 min
15:05 / 15:06≈ on time ≈ +3 min
15:10 / 15:11≈ on time ≈ +4 min
15:14≈ on time ≈ +4 min
15:18 / 15:19≈ on time ≈ +4 min
15:22 / 15:23≈ on time ≈ +4 min
15:27 / 15:28≈ on time ≈ +5 min
15:34on 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
Wed 4 NovLibourne 15:340 min—
Tue 3 NovLibourne 15:350 min—
Mon 2 NovLibourne 15:340 min—
Sun 1 NovLibourne 15:350 min—
Sat 31 OctLibourne 15:360 min—
Fri 30 OctLibourne 15:40+5 min+5 min
Thu 29 OctLibourne 15:350 min—
Wed 28 OctLibourne 15:40+5 min+5 min
Tue 27 OctLibourne 15:40+5 min+5 min
Mon 26 OctLibourne 15:360 min—
Sun 25 OctLibourne 15:350 min—
Sat 24 OctLibourne 15:350 min—
Fri 23 OctLibourne 15:350 min—
Thu 22 OctLibourne 15:350 min—
Wed 21 OctLibourne 15:350 min—
Tue 20 OctLibourne 15:350 min—
Mon 19 OctLibourne 15:360 min—
Sun 18 OctLibourne 15:350 min—
Sat 17 OctLibourne 15:350 min—
Fri 16 OctLibourne 15:350 min—
Thu 15 OctLibourne 15:350 min+5 min
Wed 14 OctLibourne 15:350 min—
Tue 13 OctLibourne 15:350 min—
Mon 12 OctLibourne 15:350 min—
Sun 11 OctLibourne 15:350 min—
Sat 10 OctLibourne 15:41+5 min+5 min
Fri 9 OctLibourne 15:350 min—
Thu 8 OctLibourne 15:350 min—
Wed 7 OctLibourne 15:40+5 min+5 min
Tue 6 OctLibourne 15:350 min—