P26 893201 Nevers – Decize

View line P26

Nevers 07:11 → Decize 07:42 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 07:11 from Nevers · Mon 9 Nov

Next departure 07:11 tomorrow · Nevers
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
96%
24/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
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Thu 22 Oct Max en route +5 min · last fix heading to Decize +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 96% · 24
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
07:11on time on time
07:14≈ on time ≈ on time
07:16 / 07:17≈ on time ≈ on time
07:25≈ on time ≈ on time
07:32≈ on time ≈ on time
07:42on 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 07:430 min—
Thu 5 NovDecize 07:430 min—
Wed 4 NovDecize 07:430 min—
Tue 3 NovDecize 07:430 min—
Mon 2 NovDecize 07:430 min—
Fri 30 OctDecize 07:430 min—
Thu 29 OctDecize 07:430 min—
Wed 28 OctDecize 07:430 min—
Tue 27 OctDecize 07:430 min—
Mon 26 OctDecize 07:430 min—
Fri 23 OctDecize 07:430 min—
Thu 22 OctDecize 07:48+5 min+5 min
Wed 21 OctDecize 07:430 min—
Tue 20 OctDecize 07:430 min—
Mon 19 OctDecize 07:430 min—
Fri 16 OctDecize 07:440 min—
Thu 15 OctDecize 07:440 min—
Wed 14 OctDecize 07:430 min—
Tue 13 OctDecize 07:430 min—
Mon 12 OctDecize 07:430 min—
Fri 9 OctDecize 07:440 min—
Thu 8 OctDecize 07:430 min—
Wed 7 OctDecize 07:440 min—
Tue 6 OctDecize 07:440 min—
Mon 5 OctStopPoint:OCETrain TE~5eb89f56 07:440 min—