P26 893205 Nevers – Decize

View line P26

Nevers 16:09 → Decize 16:40 Mon, Tue, Wed, Thu, Fri 0 h 31 min · 6 stops SNCF

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: tomorrow 16:09 from Nevers · Mon 9 Nov

Next departure 16:09 tomorrow · Nevers
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
93%
55/59 runs under 3 min
RT coverage: 59 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: +1 min

Last 30 days

Arrival delay at Decize, 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 27 Oct Max en route +15 min · last fix heading to Decize +10 min
  • Thu 8 Oct Max en route +10 min · last fix heading to Decize +10 min
  • Fri 30 Oct Max en route +5 min · last fix heading to Decize +5 min
  • Tue 6 Oct Max en route +5 min · last fix heading to Decize +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 55
  • 3–10 min 3% · 2
  • 10–30 min 3% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 82% T n=11
  • 100% W n=12
  • 92% T n=12
  • 92% F n=12
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 59 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
16:09on time on time
16:12≈ on time ≈ on time
16:14 / 16:15≈ on time ≈ on time
16:23≈ on time ≈ on time
16:30≈ on time ≈ on time
16:40on 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
Fri 6 NovDecize 16:390 min—
Thu 5 NovDecize 16:390 min—
Wed 4 NovDecize 16:390 min—
Tue 3 NovDecize 16:400 min—
Mon 2 NovDecize 16:390 min—
Fri 30 OctDecize 16:46+5 min+5 min
Thu 29 OctDecize 16:410 min—
Wed 28 OctDecize 16:410 min—
Tue 27 OctDecize 16:51+10 min+15 min
Mon 26 OctDecize 16:420 min—
Fri 23 OctDecize 16:420 min—
Thu 22 OctDecize 16:420 min—
Wed 21 OctDecize 16:410 min—
Tue 20 OctDecize 16:410 min—
Mon 19 OctDecize 16:420 min—
Fri 16 OctDecize 16:410 min—
Thu 15 OctDecize 16:410 min—
Wed 14 OctDecize 16:410 min—
Tue 13 OctDecize 16:410 min—
Mon 12 OctDecize 16:410 min—
Fri 9 OctDecize 16:410 min—
Thu 8 OctDecize 16:51+10 min+10 min
Wed 7 OctDecize 16:410 min—
Tue 6 OctDecize 16:46+5 min+5 min
Mon 5 OctDecize 16:420 min—
Fri 2 OctStopPoint:OCETrain TER-8769648 16:390 min—
Thu 1 OctStopPoint:OCETrain TER-8769648 16:390 min+10 min
Wed 30 SeptStopPoint:OCETrain TER-8769648 16:390 min—
Tue 29 SeptStopPoint:OCETrain TER-8769648 16:390 min—
Mon 28 SeptStopPoint:OCETrain TER-8769648 16:390 min+20 min