P12 893757 Cosne-sur-Loire – Nevers

View line P12

Cosne-sur-Loire 13:34 → Nevers 14:25 Mon, Tue, Thu, Fri, Sat 0 h 51 min · 10 stops SNCF

✓ Today’s run finished

Today it reached Nevers at 14:25 0 min

  1. Cosne-sur-Loire13:34
  2. Pouilly-sur-Loire13:48
  3. Mesves - Bulcy13:53
  4. Tronsanges14:05
  5. Pougues-les-Eaux14:10
  6. Vauzelles14:21
  7. Nevers14:25

Next service: tomorrow 13:34 from Cosne-sur-Loire · Tue 10 Nov

Next departure 13:34 tomorrow · Cosne-sur-Loire
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 25 full · 0 partial · 0 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 31 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 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

  • Mon 19 Oct Max en route +45 min · last fix heading to Nevers +45 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 30
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 3% · 1

On-time by weekday

  • 83% M n=6
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=5
  • — S n=0

Stops and timetable

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

Last 90 days, 31 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
13:34on time on time
13:41 / 13:42≈ on time ≈ on time
13:48≈ on time ≈ on time
13:53≈ on time ≈ on time
13:59 / 14:00≈ on time ≈ on time
14:05 / 14:06≈ on time ≈ on time
14:10 / 14:11≈ on time ≈ on time
14:16 / 14:17≈ on time ≈ on time
14:21 / 14:22≈ on time ≈ on time
14:25on 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
Mon 9 NovNevers 14:240 min—
Sat 7 NovNevers 14:240 min—
Fri 6 NovNevers 14:240 min—
Thu 5 NovNevers 14:240 min—
Wed 4 NovNevers 14:240 min—
Tue 3 NovNevers 14:240 min—
Mon 2 NovNevers 14:240 min—
Sat 31 OctNevers 14:270 min—
Fri 30 OctNevers 14:260 min—
Thu 29 OctNevers 14:260 min—
Wed 28 OctNevers 14:260 min—
Tue 27 OctNevers 14:260 min—
Mon 26 OctNevers 14:270 min—
Sat 24 OctNevers 14:260 min—
Fri 23 OctNevers 14:260 min—
Thu 22 OctNevers 14:260 min—
Wed 21 OctNevers 14:260 min—
Tue 20 OctNevers 14:260 min—
Mon 19 OctNevers 15:12+45 min+45 min
Sat 17 OctNevers 14:260 min—
Fri 16 OctNevers 14:260 min—
Thu 15 OctNevers 14:260 min—
Wed 14 OctNevers 14:260 min—
Tue 13 OctNevers 14:260 min—
Mon 12 OctNevers 14:260 min—
Sat 10 OctNevers 14:270 min—
Fri 9 OctNevers 14:260 min—
Thu 8 OctNevers 14:260 min—
Wed 7 OctNevers 14:260 min—
Tue 6 OctNevers 14:260 min—