560A 3628 Brive-la-Gaillarde – Paris Austerlitz

View line 560A

Brive-la-Gaillarde 07:04 → Paris Austerlitz 11:30 Sun 4 h 26 min · 7 stops SNCF

It does not run today

Last recorded run: Sunday 1 November 0 min

Next service: Sunday 07:04 from Brive-la-Gaillarde · Sun 8 Nov

Next departure 07:04 Sunday · Brive-la-Gaillarde
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 13 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Paris Austerlitz, 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 4 Oct Max en route +10 min · last fix heading to StopPoint:OCEINTERCIT~58cb443f +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 0% · 0
  • 10–30 min 8% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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
07:04on time on time
08:05 / 08:08≈ on time ≈ +2 min
08:38 / 08:40≈ on time ≈ +3 min
09:04 / 09:06≈ on time ≈ +4 min
09:22 / 09:24≈ on time ≈ +4 min
10:28 / 10:30≈ on time ≈ +2 min
11:30on 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 1 NovParis Austerlitz 11:310 min+5 min
Sun 25 OctParis Austerlitz 11:310 min—
Sun 18 OctParis Austerlitz 11:310 min—
Sun 11 OctParis Austerlitz 11:530 min—
Sun 4 OctStopPoint:OCEINTERCIT~58cb443f 11:46+10 min+10 min
Sun 27 SeptStopPoint:OCEINTERCITES-876866 11:340 min+5 min
Sun 20 SeptStopPoint:OCEINTERCITES-875470 11:300 min—
Sun 13 SeptStopPoint:OCEINTERCITES-875470 11:290 min+10 min
Sun 6 SeptStopPoint:OCEINTERCITES-875470 11:290 min—
Sun 30 AugStopPoint:OCEINTERCITES-875470 11:290 min—
Sun 23 AugStopPoint:OCEINTERCITES-875470 11:290 min—
Sun 16 AugStopPoint:OCEINTERCITES-875470 11:300 min+10 min
Sun 9 AugStopPoint:OCEINTERCITES-875470 11:290 min—