P26 893204 Decize – Nevers

View line P26

Decize 08:19 → Nevers 08:50 Mon, Tue, Wed, Thu, Fri 0 h 31 min · 6 stops SNCF

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 08:19 from Decize · Fri 6 Nov

Next departure 08:19 today · Decize
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 24 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

  • Thu 8 Oct Max en route +5 min · last fix heading to Nevers +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 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=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 24 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
08:19on time on time
08:27 / 08:28≈ on time ≈ on time
08:34 / 08:35≈ on time ≈ on time
08:42 / 08:43≈ on time ≈ on time
08:45 / 08:46≈ on time ≈ on time
08:50on 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
Thu 5 NovNevers 08:490 min—
Wed 4 NovNevers 08:490 min—
Tue 3 NovNevers 08:490 min—
Mon 2 NovNevers 08:490 min—
Fri 30 OctNevers 08:510 min—
Thu 29 OctNevers 08:510 min—
Wed 28 OctNevers 08:510 min—
Tue 27 OctNevers 08:510 min—
Mon 26 OctNevers 08:510 min—
Fri 23 OctNevers 08:510 min—
Thu 22 OctNevers 08:510 min—
Wed 21 OctNevers 08:510 min—
Tue 20 OctNevers 08:510 min—
Mon 19 OctNevers 08:510 min—
Fri 16 OctNevers 08:510 min—
Thu 15 OctNevers 08:510 min—
Wed 14 OctNevers 08:510 min—
Tue 13 OctNevers 08:510 min—
Mon 12 OctNevers 08:520 min—
Fri 9 OctNevers 08:520 min—
Thu 8 OctNevers 08:56+5 min+5 min
Wed 7 OctNevers 08:520 min—
Tue 6 OctNevers 08:510 min—
Mon 5 OctStopPoint:OCETrain TE~285aa43c 08:520 min—