P14 861610 Bourges – Nevers

View line P14

Bourges 12:23 → Nevers 13:13 Daily 0 h 50 min · 7 stops SNCF

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 12:23 from Bourges · Fri 6 Nov

Next departure 12:23 today · Bourges
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 12 full · 0 partial · 0 no data
On-time · 90 days
98%
40/41 runs under 3 min
RT coverage: 41 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

  • Wed 19 Aug Max en route +30 min · last fix heading to StopPoint:OCETrain TER-8757647 +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 40
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 83% W n=6
  • 100% T n=6
  • 100% F n=2
  • 100% S n=5
  • 100% S n=10

Stops and timetable

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

Last 90 days, 42 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
12:23on time on time
12:28 / 12:29≈ on time ≈ on time
12:37 / 12:38≈ on time ≈ on time
12:43 / 12:44≈ on time ≈ on time
12:49 / 12:50≈ on time ≈ on time
12:59 / 13:00≈ on time ≈ on time
13:13on 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 13:140 min—
Wed 4 NovNevers 13:140 min—
Tue 3 NovNevers 13:150 min—
Mon 2 NovNevers 13:140 min—
Sun 1 NovNevers 13:140 min—
Sat 31 OctNevers 13:140 min—
Sun 25 OctNevers 13:140 min—
Sat 24 OctNevers 13:140 min—
Sun 18 OctNevers 13:140 min—
Sat 17 OctNevers 13:140 min—
Sun 11 OctNevers 13:140 min—
Sat 10 OctNevers 13:150 min—
Sun 4 OctStopPoint:OCETrain TE~285aa43c 13:140 min—
Sun 27 SeptStopPoint:OCETrain TER-8769600 13:120 min—
Thu 10 SeptStopPoint:OCETrain TER-8769600 13:120 min—
Wed 9 SeptStopPoint:OCETrain TER-8769600 13:120 min—
Tue 8 SeptStopPoint:OCETrain TER-8769600 13:120 min+20 min
Mon 7 SeptStopPoint:OCETrain TER-8769600 13:120 min—
Thu 3 SeptStopPoint:OCETrain TER-8769600 13:120 min—
Wed 2 SeptStopPoint:OCETrain TER-8769600 13:130 min—
Tue 1 SeptStopPoint:OCETrain TER-8769600 13:120 min—
Mon 31 AugStopPoint:OCETrain TER-8769600 13:120 min—
Sun 30 AugStopPoint:OCETrain TER-8769600 13:120 min—
Thu 27 AugStopPoint:OCETrain TER-8769600 13:120 min—
Wed 26 AugStopPoint:OCETrain TER-8769600 13:120 min—
Tue 25 AugStopPoint:OCETrain TER-8769600 13:130 min+30 min
Mon 24 AugStopPoint:OCETrain TER-8769600 13:120 min—
Sun 23 AugStopPoint:OCETrain TER-8769600 13:120 min—
Fri 21 AugStopPoint:OCETrain TER-8769600 13:120 min—
Thu 20 AugStopPoint:OCETrain TER-8769600 13:120 min—