L12 863232 Angoulême – Poitiers

View line L12

Angoulême 12:42 → Poitiers 13:59 Wed, Sat, Sun 1 h 17 min · 9 stops SNCF

✓ Today’s run finished

Today it reached Poitiers at 13:59 0 min

  1. Angoulême12:42
  2. Luxé12:57
  3. Saint-Saviol13:18
  4. Anché - Voulon13:30
  5. Vivonne13:37
  6. Ligugé13:50
  7. Poitiers13:59

Next service: Wednesday 12:42 from Angoulême · Wed 11 Nov

Next departure 12:42 Wednesday · Angoulême
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 26 full · 0 partial · 0 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 Poitiers, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 6 Sept Max en route +5 min · last fix heading to StopPoint:OCETrain TER-8757500 +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 96% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=13
  • 92% S n=13

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
12:42on time +3 min
12:57 / 12:58≈ on time ≈ +3 min
13:09 / 13:10≈ on time ≈ +3 min
13:18 / 13:19≈ on time ≈ +3 min
13:30 / 13:31≈ on time ≈ +2 min
13:37 / 13:38≈ on time ≈ +1 min
13:45 / 13:46≈ on time ≈ +1 min
13:50 / 13:51≈ on time ≈ +1 min
13:59on 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
Sun 8 NovPoitiers 13:590 min—
Sat 7 NovPoitiers 13:590 min—
Sun 1 NovPoitiers 14:000 min—
Sat 31 OctPoitiers 14:000 min+5 min
Sun 25 OctPoitiers 14:000 min—
Sat 24 OctPoitiers 14:000 min—
Sun 18 OctPoitiers 14:010 min—
Sat 17 OctPoitiers 14:000 min—
Sun 11 OctPoitiers 14:000 min—
Sat 10 OctPoitiers 14:010 min—
Sun 4 OctStopPoint:OCETrain TE~43650e0b 14:000 min+5 min
Sat 3 OctStopPoint:OCETrain TER-8757500 13:580 min—
Sun 27 SeptStopPoint:OCETrain TER-8757500 13:580 min—
Sat 26 SeptStopPoint:OCETrain TER-8757500 13:580 min—
Sun 20 SeptStopPoint:OCETrain TER-8757500 13:590 min—
Sat 19 SeptStopPoint:OCETrain TER-8757500 13:580 min—
Sun 13 SeptStopPoint:OCETrain TER-8757500 13:580 min—
Sat 12 SeptStopPoint:OCETrain TER-8757500 13:580 min—
Sun 6 SeptStopPoint:OCETrain TER-8757500 13:58+5 min+5 min
Sat 5 SeptStopPoint:OCETrain TER-8757500 13:580 min—
Sun 30 AugStopPoint:OCETrain TER-8757500 13:580 min+20 min
Sat 29 AugStopPoint:OCETrain TER-8757500 13:580 min+70 min
Sun 23 AugStopPoint:OCETrain TER-8757500 13:580 min—
Sat 22 AugStopPoint:OCETrain TER-8757500 13:580 min+5 min
Sun 16 AugStopPoint:OCETrain TER-8757500 13:590 min—
Sat 15 AugStopPoint:OCETrain TER-8757500 13:580 min—