L34 865891 Monsempron-Libos – Agen

View line L34

Monsempron-Libos 18:07 → Agen 18:56 Mon, Tue, Wed, Thu, Fri 0 h 49 min · 4 stops SNCF

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 18:07 from Monsempron-Libos · Mon 9 Nov

Next departure 18:07 today · Monsempron-Libos
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 15 full · 0 partial · 1 no data
On-time · 90 days
73%
29/40 runs under 3 min
RT coverage: 40 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: +3 min

Last 30 days

Arrival delay at Agen, 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 5 Oct Max en route +30 min · last fix heading to Agen +25 min
  • Mon 31 Aug Max en route +20 min · last fix heading to StopPoint:OCETrain TER-8758641 +20 min
  • Tue 15 Sept Max en route +15 min · last fix heading to StopPoint:OCETrain TER-8758600 +15 min
  • Thu 15 Oct Max en route +10 min · last fix heading to Agen +10 min
  • Thu 8 Oct Max en route +10 min · last fix heading to Agen +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 73% · 29
  • 3–10 min 15% · 6
  • 10–30 min 13% · 5
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=9
  • 89% T n=9
  • 57% W n=7
  • 60% T n=10
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 40 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
18:07on time on time
18:19 / 18:22≈ on time ≈ +4 min
18:38 / 18:39≈ on time ≈ +7 min
18:56on 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 6 NovAgen 18:570 min—
Thu 5 NovAgen 18:57No data—
Tue 3 NovAgen 18:580 min—
Fri 30 OctAgen 18:570 min—
Thu 29 OctAgen 18:570 min—
Wed 28 OctAgen 19:02+5 min+5 min
Tue 27 OctAgen 18:570 min—
Fri 23 OctAgen 18:580 min—
Thu 22 OctAgen 18:580 min—
Wed 21 OctAgen 18:570 min—
Mon 19 OctAgen 18:570 min—
Fri 16 OctAgen 18:570 min—
Thu 15 OctAgen 19:07+10 min+10 min
Wed 14 OctAgen 18:570 min—
Tue 13 OctAgen 18:570 min—
Mon 12 OctAgen 18:570 min—
Fri 9 OctAgen 18:570 min—
Thu 8 OctAgen 19:07+10 min+10 min
Tue 6 OctAgen 18:570 min—
Mon 5 OctAgen 19:22+25 min+30 min
Tue 29 SeptStopPoint:OCETrain TER-8758600 18:550 min+15 min
Thu 24 SeptStopPoint:OCETrain TER-8758600 18:56+5 min+5 min
Wed 23 SeptStopPoint:OCETrain TER-8758600 18:55+5 min+5 min
Tue 22 SeptStopPoint:OCETrain TER-8758600 18:550 min—
Mon 21 SeptStopPoint:OCETrain TER-8758600 18:55+5 min+5 min
Thu 17 SeptStopPoint:OCETrain TER-8758600 18:550 min—
Wed 16 SeptStopPoint:OCETrain TER-8758600 18:55+5 min+5 min
Tue 15 SeptStopPoint:OCETrain TER-8758600 18:55+15 min+15 min
Mon 14 SeptStopPoint:OCETrain TER-8758600 18:550 min+5 min
Wed 9 SeptStopPoint:OCETrain TER-8758600 18:550 min+40 min