K5+ 3923 Paris Austerlitz – Nevers

View line K5+

Paris Austerlitz 21:07 → Nevers 23:44 Wed, Fri, Sun 2 h 37 min · 6 stops SNCF

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: tomorrow 21:07 from Paris Austerlitz · Sun 8 Nov

Next departure 21:07 tomorrow · Paris Austerlitz
On-time · 30 days
67%
6/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
On-time · 90 days
68%
17/25 runs under 3 min
RT coverage: 25 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +20 min

Last 30 days

Arrival delay at Nevers, 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 11 Sept Max en route +90 min · last fix heading to StopPoint:OCETrain TER-8754316 +90 min
  • Sun 25 Oct Max en route +80 min · last fix heading to Nevers +80 min
  • Sun 18 Oct Max en route +5 min · last fix heading to Nevers +5 min
  • Fri 16 Oct Max en route +5 min · last fix heading to Nevers +5 min
  • Fri 25 Sept Max en route +5 min · last fix heading to StopPoint:OCETrain TER-8769600 +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 68% · 17
  • 3–10 min 24% · 6
  • 10–30 min 0% · 0
  • 30+ min 8% · 2

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • 77% F n=13
  • — S n=0
  • 58% S n=12

Stops and timetable

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

Last 90 days, 25 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
21:07on time on time
22:05 / 22:08≈ on time ≈ +8 min
22:31 / 22:33≈ on time ≈ +7 min
22:45 / 22:47≈ on time ≈ +7 min
23:04 / 23:06≈ on time ≈ +6 min
23:44on time +5 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 NovNevers 23:440 min—
Sun 1 NovNevers 23:390 min+5 min
Fri 30 OctNevers 23:450 min—
Sun 25 OctNevers 00:36+80 min+80 min
Fri 23 OctNevers 23:460 min—
Sun 18 OctNevers 23:45+5 min+5 min
Fri 16 OctNevers 23:50+5 min+5 min
Sun 11 OctNevers 23:480 min—
Fri 9 OctNevers 23:450 min—
Sun 4 OctStopPoint:OCETrain TE~285aa43c 23:400 min—
Fri 2 OctStopPoint:OCETrain TER-8769600 23:430 min+10 min
Sun 27 SeptStopPoint:OCETrain TER-8769600 23:380 min—
Fri 25 SeptStopPoint:OCETrain TER-8769600 23:42+5 min+5 min
Sun 20 SeptStopPoint:OCETrain TER-8769600 23:38+5 min+5 min
Fri 18 SeptStopPoint:OCETrain TER-8769600 23:420 min—
Sun 13 SeptStopPoint:OCETrain TER-8769600 23:370 min—
Fri 11 SeptStopPoint:OCETrain TER-8754316 23:42+90 min+90 min
Sun 6 SeptStopPoint:OCETrain TER-8769600 23:37+5 min+15 min
Fri 4 SeptStopPoint:OCETrain TER-8769600 23:420 min—
Sun 30 AugStopPoint:OCETrain TER-8769600 23:370 min—
Fri 28 AugStopPoint:OCETrain TER-8769600 23:420 min—
Sun 23 AugStopPoint:OCETrain TER-8769600 23:37+5 min+5 min
Fri 21 AugStopPoint:OCETrain TER-8769600 23:420 min—
Sun 16 AugStopPoint:OCETrain TER-8769600 23:370 min—
Fri 14 AugStopPoint:OCETrain TER-8769600 23:420 min+5 min