F41+ 866202 Arcachon – Libourne

View line F41+

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

✓ Today’s run finished

Today it reached Libourne at 07:10 +5 min

  1. Arcachon05:35
  2. Gujan-Mestras05:46
  3. Marcheprime06:03
  4. Pessac06:19
  5. Cenon06:36
  6. Saint-Loubès06:49
  7. Libourne07:05

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

Next departure 05:35 Monday · Arcachon
On-time · 30 days
61%
11/18 runs under 3 min
RT coverage: 18 full · 0 partial · 1 no data
On-time · 90 days
69%
18/26 runs under 3 min
RT coverage: 26 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

  • Fri 30 Oct Max en route +10 min · last fix heading to Libourne +10 min
  • Wed 14 Oct Max en route +10 min · last fix heading to Libourne +10 min
  • Fri 13 Nov Max en route +5 min · last fix heading to Libourne +5 min
  • Tue 3 Nov Max en route +5 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

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

  • Early 0% · 0
  • On time 69% · 18
  • 3–10 min 23% · 6
  • 10–30 min 8% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 67% T n=6
  • 75% W n=4
  • 80% T n=5
  • 60% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 26 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
05:35on time on time
05:38 / 05:39≈ on time ≈ on time
05:41 / 05:42≈ on time ≈ on time
05:46 / 05:47≈ on time ≈ +1 min
05:50 / 05:51≈ on time ≈ +1 min
05:56 / 05:57≈ on time ≈ +1 min
06:03 / 06:04≈ on time ≈ +2 min
06:12 / 06:13≈ on time ≈ +2 min
06:16 / 06:17≈ on time ≈ +2 min
06:19 / 06:20≈ on time ≈ +2 min
06:22 / 06:23≈ on time ≈ +3 min
06:28 / 06:33≈ on time ≈ +3 min
06:36 / 06:37≈ on time ≈ +3 min
06:41 / 06:42≈ on time ≈ +4 min
06:45≈ on time ≈ +4 min
06:49 / 06:50≈ on time ≈ +4 min
06:53 / 06:54≈ on time ≈ +4 min
06:58 / 06:59≈ on time ≈ +5 min
07:05on 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 07:09+5 min+5 min
Thu 12 NovLibourne 07:040 min—
Tue 10 NovLibourne 07:040 min—
Mon 9 NovLibourne 07:040 min—
Thu 5 NovLibourne 07:04No data—
Tue 3 NovLibourne 07:09+5 min+5 min
Mon 2 NovLibourne 07:09+5 min+5 min
Fri 30 OctLibourne 07:16+10 min+10 min
Thu 29 OctLibourne 07:060 min—
Wed 28 OctLibourne 07:060 min—
Tue 27 OctLibourne 07:060 min—
Mon 26 OctLibourne 07:060 min—
Fri 23 OctLibourne 07:060 min—
Thu 22 OctLibourne 07:060 min—
Wed 21 OctLibourne 07:060 min—
Tue 20 OctLibourne 07:11+5 min+5 min
Mon 19 OctLibourne 07:11+5 min+5 min
Fri 16 OctLibourne 07:060 min—
Thu 15 OctLibourne 07:12+5 min+10 min
Wed 14 OctLibourne 07:16+10 min+10 min
Tue 13 OctLibourne 07:060 min—
Mon 12 OctLibourne 07:060 min—
Fri 9 OctLibourne 07:070 min—
Thu 8 OctLibourne 07:060 min—
Wed 7 OctLibourne 07:060 min—
Tue 6 OctLibourne 07:070 min—
Mon 5 OctStopPoint:OCETrain TE~05100f6f 07:070 min—