K5+ 3913 Paris Austerlitz – Nevers

View line K5+

Paris Austerlitz 17:07 → Nevers 19:45 Mon, Tue, Wed, Thu, Fri, Sun 2 h 38 min · 6 stops SNCF

It has not run yet today

Last recorded run: Wednesday 11 November 0 min

Next service: today 17:07 from Paris Austerlitz · Thu 12 Nov

Next departure 17:07 today · Paris Austerlitz
On-time · 30 days
64%
16/25 runs under 3 min
RT coverage: 25 full · 0 partial · 0 no data
On-time · 90 days
73%
36/49 runs under 3 min
RT coverage: 49 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +10 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

  • Tue 10 Nov Max en route +70 min · last fix heading to Bourges +70 min
  • Mon 9 Nov Max en route +15 min · last fix heading to Nevers +10 min
  • Fri 23 Oct Max en route +10 min · last fix heading to Nevers +10 min
  • Mon 19 Oct Max en route +10 min · last fix heading to Nevers +10 min
  • Sun 4 Oct Max en route +15 min · last fix heading to StopPoint:OCETrain TE~285aa43c +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 73% · 36
  • 3–10 min 16% · 8
  • 10–30 min 8% · 4
  • 30+ min 2% · 1

On-time by weekday

  • 75% M n=8
  • 78% T n=9
  • 89% W n=9
  • 71% T n=7
  • 71% F n=7
  • — S n=0
  • 56% S n=9

Stops and timetable

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

Last 90 days, 49 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
17:07on time on time
18:03 / 18:06≈ on time ≈ +4 min
18:29 / 18:31≈ on time ≈ +5 min
18:44 / 18:46≈ on time ≈ +6 min
19:03 / 19:06≈ on time ≈ +5 min
19:45on time +6 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
Wed 11 NovNevers 19:440 min—
Tue 10 NovBourges 20:14+70 min+70 min
Mon 9 NovNevers 19:54+10 min+15 min
Sun 8 NovNevers 19:440 min—
Fri 6 NovNevers 19:450 min—
Thu 5 NovNevers 19:470 min—
Wed 4 NovNevers 19:440 min—
Tue 3 NovNevers 19:450 min—
Mon 2 NovNevers 19:440 min—
Sun 1 NovNevers 19:440 min—
Fri 30 OctNevers 19:460 min—
Thu 29 OctNevers 19:460 min—
Wed 28 OctNevers 19:460 min+15 min
Tue 27 OctNevers 19:460 min+5 min
Mon 26 OctNevers 19:470 min—
Sun 25 OctNevers 19:51+5 min+5 min
Fri 23 OctNevers 19:57+10 min+10 min
Thu 22 OctNevers 19:51+5 min+10 min
Wed 21 OctNevers 19:51+5 min+5 min
Tue 20 OctNevers 19:460 min—
Mon 19 OctNevers 19:56+10 min+10 min
Sun 18 OctNevers 19:51+5 min+5 min
Fri 16 OctNevers 19:51+5 min+5 min
Thu 15 OctNevers 19:460 min—
Wed 14 OctNevers 19:460 min—
Tue 13 OctNevers 19:460 min—
Mon 12 OctNevers 19:460 min—
Sun 11 OctNevers 19:51+5 min+5 min
Fri 9 OctNevers 19:460 min—
Thu 8 OctNevers 19:470 min—