F41+ 866222 Arcachon – Libourne

View line F41+

Arcachon 10:05 → Libourne 11:35 Mon, Tue, Wed, Thu, Fri 1 h 30 min · 19 stops SNCF

It does not run today

Last recorded run: Friday 13 November +5 min

Next service: Monday 10:05 from Arcachon · Mon 16 Nov

Next departure 10:05 Monday · Arcachon
On-time · 30 days
68%
13/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
75%
36/48 runs under 3 min
RT coverage: 48 full · 0 partial · 1 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

  • Mon 24 Aug Max en route +15 min · last fix heading to StopPoint:OCETrain TER-8758473 +15 min
  • Thu 12 Nov Max en route +10 min · last fix heading to Libourne +10 min
  • Wed 7 Oct Max en route +10 min · last fix heading to Libourne +10 min
  • Fri 13 Nov Max en route +10 min · last fix heading to Libourne +5 min
  • Mon 2 Nov Max en route +5 min · last fix heading to Libourne +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 36
  • 3–10 min 19% · 9
  • 10–30 min 6% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=10
  • 80% T n=10
  • 78% W n=9
  • 78% T n=9
  • 60% F n=10
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 48 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
10:05on time on time
10:08 / 10:09≈ on time ≈ on time
10:11 / 10:12≈ on time ≈ on time
10:16 / 10:17≈ on time ≈ +1 min
10:20 / 10:21≈ on time ≈ +1 min
10:26 / 10:27≈ on time ≈ +1 min
10:33 / 10:34≈ on time ≈ +2 min
10:42 / 10:43≈ on time ≈ +2 min
10:46 / 10:47≈ on time ≈ +2 min
10:49 / 10:50≈ on time ≈ +2 min
10:52 / 10:53≈ on time ≈ +3 min
10:58 / 11:02≈ on time ≈ +3 min
11:05 / 11:06≈ on time ≈ +3 min
11:10 / 11:11≈ on time ≈ +4 min
11:14 / 11:15≈ on time ≈ +4 min
11:19 / 11:20≈ on time ≈ +4 min
11:23 / 11:24≈ on time ≈ +4 min
11:28 / 11:29≈ on time ≈ +5 min
11:35on 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
Fri 13 NovLibourne 11:39+5 min+10 min
Thu 12 NovLibourne 11:44+10 min+10 min
Tue 10 NovLibourne 11:340 min—
Mon 9 NovLibourne 11:340 min—
Fri 6 NovLibourne 11:340 min—
Thu 5 NovLibourne 11:34No data—
Wed 4 NovLibourne 11:340 min—
Tue 3 NovLibourne 11:370 min—
Mon 2 NovLibourne 11:39+5 min+5 min
Fri 30 OctLibourne 11:360 min—
Thu 29 OctLibourne 11:360 min—
Wed 28 OctLibourne 11:360 min—
Tue 27 OctLibourne 11:41+5 min+5 min
Mon 26 OctLibourne 11:360 min—
Fri 23 OctLibourne 11:41+5 min+5 min
Thu 22 OctLibourne 11:360 min—
Wed 21 OctLibourne 11:360 min—
Tue 20 OctLibourne 11:41+5 min+5 min
Mon 19 OctLibourne 11:360 min—
Fri 16 OctLibourne 11:360 min—
Thu 15 OctLibourne 11:360 min—
Wed 14 OctLibourne 11:360 min—
Tue 13 OctLibourne 11:360 min—
Mon 12 OctLibourne 11:370 min—
Fri 9 OctLibourne 11:370 min—
Thu 8 OctLibourne 11:360 min—
Wed 7 OctLibourne 11:46+10 min+10 min
Tue 6 OctLibourne 11:360 min—
Mon 5 OctStopPoint:OCETrain TE~05100f6f 11:360 min—
Fri 2 OctStopPoint:OCETrain TER-8758405 11:34+5 min+5 min