L34 865881 Monsempron-Libos – Agen

View line L34

Monsempron-Libos 09:55 → Agen 10:40 Mon, Tue, Thu, Fri 0 h 45 min · 4 stops SNCF

✓ Today’s run finished

Today it reached Agen at 10:40 0 min

  1. Monsempron-Libos09:55
  2. Penne10:07
  3. Laroque10:21
  4. Agen10:40

Next service: Thursday 09:55 from Monsempron-Libos · Thu 12 Nov

Next departure 09:55 Thursday · Monsempron-Libos
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 16 full · 0 partial · 1 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 16 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Fri 23 Oct Max en route +5 min · last fix heading to Agen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=4
  • 100% T n=2
  • 50% F n=2
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 16 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
09:55on time on time
10:07 / 10:08≈ on time ≈ on time
10:21 / 10:22≈ on time ≈ on time
10:40on time on time

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
Tue 10 NovAgen 10:390 min—
Mon 9 NovAgen 10:410 min—
Thu 5 NovAgen 10:39No data—
Wed 4 NovAgen 10:390 min—
Tue 3 NovAgen 10:400 min—
Wed 28 OctAgen 10:410 min—
Tue 27 OctAgen 10:410 min—
Fri 23 OctAgen 10:46+5 min+5 min
Thu 22 OctAgen 10:410 min—
Wed 21 OctAgen 10:410 min—
Tue 20 OctAgen 10:410 min—
Mon 19 OctAgen 10:410 min—
Fri 16 OctAgen 10:410 min—
Thu 15 OctAgen 10:410 min—
Wed 14 OctAgen 10:410 min—
Tue 13 OctAgen 10:410 min—
Mon 12 OctAgen 10:420 min—