K2+ 5909 Paris Bercy Bourg. Pays d'Auv. → Nevers

View line K2+

Paris Bercy Bourg. Pays d'Auv. 14:11 → Nevers 16:36 Mon, Tue, Wed, Thu, Fri, Sat 2 h 25 min · 11 stops SNCF

TER 5909 Paris Bercy Bourg. Pays d'Auv.–Nevers: final delay under 3 min on 16 of its 23 runs with data in the last 30 days (70%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 13:08 (GMT+1).

It does not run today

Last recorded run: Saturday 21 November 0 min

Next service: tomorrow 14:11 from Paris Bercy Bourg. Pays d'Auv. · Mon 23 Nov

Next departure 14:11 tomorrow · Paris Bercy Bourg. Pays d'Auv.
On-time · 30 days
70%
16/23 runs under 3 min
RT coverage: 23 full · 0 partial · 0 no data
On-time · 90 days
72%
39/54 runs under 3 min
RT coverage: 54 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+14min
9 in 10 runs arrive with less than this
30 days: +5 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 20 Nov Max en route +80 min · last fix heading to Nevers +80 min
  • Fri 23 Oct Max en route +80 min · last fix heading to Nevers +80 min
  • Mon 2 Nov Max en route +20 min · last fix heading to Nevers +20 min
  • Thu 15 Oct Max en route +20 min · last fix heading to Nevers +20 min
  • Tue 13 Oct Max en route +15 min · last fix heading to Nevers +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 72% · 39
  • 3–10 min 13% · 7
  • 10–30 min 11% · 6
  • 30+ min 4% · 2

On-time by weekday

  • 67% M n=12
  • 86% T n=7
  • 67% W n=12
  • 57% T n=7
  • 71% F n=7
  • 89% S n=9
  • — S n=0

Stops and timetable

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

Last 90 days, 54 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
14:11on time on time
15:10 / 15:12≈ on time ≈ +5 min
15:22 / 15:23≈ on time ≈ +7 min
15:33 / 15:34≈ on time ≈ +8 min
15:40 / 15:41≈ on time ≈ +8 min
15:56 / 15:57≈ on time ≈ +10 min
16:03 / 16:04≈ on time ≈ +10 min
16:15 / 16:16≈ on time ≈ +12 min
16:24 / 16:25≈ on time ≈ +12 min
16:29 / 16:30≈ on time ≈ +13 min
16:36on time +14 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
Sat 21 NovNevers 16:370 min—
Fri 20 NovNevers 17:58+80 min+80 min
Thu 19 NovNevers 16:42+5 min+5 min
Wed 18 NovNevers 16:370 min—
Tue 17 NovNevers 16:370 min—
Mon 16 NovNevers 16:43+5 min+5 min
Sat 14 NovNevers 16:370 min—
Fri 13 NovNevers 16:380 min—
Thu 12 NovNevers 16:370 min—
Tue 10 NovNevers 16:370 min—
Mon 9 NovNevers 16:370 min—
Sat 7 NovNevers 16:370 min—
Fri 6 NovNevers 16:370 min—
Thu 5 NovNevers 16:370 min—
Wed 4 NovNevers 16:370 min—
Tue 3 NovNevers 16:380 min—
Mon 2 NovNevers 16:57+20 min+20 min
Fri 30 OctNevers 16:370 min—
Thu 29 OctNevers 16:42+5 min+5 min
Wed 28 OctNevers 16:370 min—
Tue 27 OctNevers 16:370 min—
Mon 26 OctNevers 16:43+5 min+5 min
Sat 24 OctNevers 16:42+5 min+5 min
Fri 23 OctNevers 17:58+80 min+80 min
Thu 22 OctNevers 16:370 min—
Wed 21 OctNevers 16:42+5 min+5 min
Tue 20 OctNevers 16:370 min—
Mon 19 OctNevers 16:380 min—
Sat 17 OctNevers 16:370 min—
Fri 16 OctNevers 16:370 min—