F41+ 866250 Arcachon – Libourne

View line F41+

Arcachon 17:35 → Libourne 19:01 Daily 1 h 26 min · 19 stops SNCF

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 17:35 from Arcachon · Sat 14 Nov

Next departure 17:35 today · Arcachon
On-time · 30 days
70%
19/27 runs under 3 min
RT coverage: 27 full · 0 partial · 1 no data
On-time · 90 days
75%
52/69 runs under 3 min
RT coverage: 69 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+10min
9 in 10 runs arrive with less than this
30 days: +7 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 28 Sept Max en route +50 min · last fix heading to StopPoint:OCETrain TER-8758240 +50 min
  • Mon 9 Nov Max en route +40 min · last fix heading to Libourne +40 min
  • Sat 26 Sept Max en route +25 min · last fix heading to StopPoint:OCETrain TER-8758475 +25 min
  • Mon 12 Oct Max en route +20 min · last fix heading to Libourne +20 min
  • Sat 10 Oct Max en route +20 min · last fix heading to Libourne +20 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 52
  • 3–10 min 12% · 8
  • 10–30 min 10% · 7
  • 30+ min 3% · 2

On-time by weekday

  • 40% M n=10
  • 100% T n=9
  • 88% W n=8
  • 100% T n=8
  • 62% F n=13
  • 58% S n=12
  • 100% S n=9

Stops and timetable

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

Last 90 days, 69 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
17:35on time +1 min
17:38 / 17:39≈ on time ≈ +2 min
17:41≈ on time ≈ +4 min
17:45 / 17:46≈ on time ≈ +4 min
17:49 / 17:50≈ on time ≈ +4 min
17:54 / 17:55≈ on time ≈ +5 min
18:01 / 18:02≈ on time ≈ +5 min
18:10 / 18:11≈ on time ≈ +5 min
18:14 / 18:15≈ on time ≈ +5 min
18:17 / 18:18≈ on time ≈ +5 min
18:21 / 18:22≈ on time ≈ +6 min
18:26 / 18:30≈ on time ≈ +6 min
18:33 / 18:34≈ on time ≈ +7 min
18:38 / 18:39≈ on time ≈ +8 min
18:42≈ on time ≈ +8 min
18:46 / 18:47≈ on time ≈ +8 min
18:50 / 18:51≈ on time ≈ +9 min
18:55 / 18:56≈ on time ≈ +9 min
19:01on time +10 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 19:030 min—
Thu 12 NovLibourne 19:020 min—
Wed 11 NovLibourne 19:020 min—
Tue 10 NovLibourne 19:020 min—
Mon 9 NovLibourne 19:42+40 min+40 min
Sun 8 NovLibourne 19:020 min—
Sat 7 NovLibourne 19:020 min—
Fri 6 NovLibourne 19:13+10 min+10 min
Thu 5 NovLibourne 19:02No data—
Tue 3 NovLibourne 19:030 min—
Mon 2 NovLibourne 19:020 min—
Sun 1 NovLibourne 19:020 min—
Sat 31 OctLibourne 19:030 min—
Fri 30 OctLibourne 19:07+5 min+5 min
Thu 29 OctLibourne 19:020 min—
Wed 28 OctLibourne 19:020 min—
Tue 27 OctLibourne 19:020 min—
Mon 26 OctLibourne 19:08+5 min+5 min
Sun 25 OctLibourne 19:020 min—
Sat 24 OctLibourne 19:020 min—
Fri 23 OctLibourne 19:13+10 min+10 min
Thu 22 OctLibourne 19:030 min—
Wed 21 OctLibourne 19:07+5 min+5 min
Tue 20 OctLibourne 19:020 min—
Mon 19 OctLibourne 19:020 min—
Sun 18 OctLibourne 19:020 min—
Sat 17 OctLibourne 19:07+5 min+10 min
Fri 16 OctLibourne 19:07+5 min+5 min
Thu 15 OctLibourne 19:020 min+5 min
Wed 14 OctLibourne 19:020 min—