P14 861566 Bourges – Vierzon

View line P14

Bourges 15:08 → Vierzon 15:35 Mon, Tue, Wed, Thu, Fri 0 h 27 min · 6 stops SNCF

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 15:08 from Bourges · Thu 5 Nov

Next departure 15:08 today · Bourges
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
95%
59/62 runs under 3 min
RT coverage: 62 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: +5 min

Last 30 days

Arrival delay at Vierzon, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 23 Oct Max en route +10 min · last fix heading to Vierzon +10 min
  • Fri 30 Oct Max en route +5 min · last fix heading to Vierzon +5 min
  • Wed 7 Oct Max en route +5 min · last fix heading to Vierzon +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 59
  • 3–10 min 3% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=13
  • 100% T n=13
  • 92% W n=13
  • 100% T n=11
  • 83% 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, 62 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
15:08on time on time
15:13 / 15:14≈ on time ≈ on time
15:19 / 15:20≈ on time ≈ on time
15:24 / 15:25≈ on time ≈ on time
15:29 / 15:30≈ on time ≈ on time
15:35on 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
Wed 4 NovVierzon 15:340 min—
Tue 3 NovVierzon 15:350 min—
Mon 2 NovVierzon 15:340 min—
Fri 30 OctVierzon 15:41+5 min+5 min
Wed 28 OctVierzon 15:360 min—
Tue 27 OctVierzon 15:360 min—
Mon 26 OctVierzon 15:370 min—
Fri 23 OctVierzon 15:46+10 min+10 min
Thu 22 OctVierzon 15:360 min—
Wed 21 OctVierzon 15:360 min—
Tue 20 OctVierzon 15:360 min—
Mon 19 OctVierzon 15:370 min—
Fri 16 OctVierzon 15:360 min—
Thu 15 OctVierzon 15:360 min—
Wed 14 OctVierzon 15:360 min—
Tue 13 OctVierzon 15:360 min—
Mon 12 OctVierzon 15:360 min—
Fri 9 OctVierzon 15:360 min—
Thu 8 OctVierzon 15:360 min—
Wed 7 OctVierzon 15:41+5 min+5 min
Tue 6 OctVierzon 15:360 min—
Mon 5 OctVierzon 15:360 min—
Fri 2 OctStopPoint:OCETrain TER-8757600 15:340 min—
Thu 1 OctStopPoint:OCETrain TER-8757600 15:340 min—
Wed 30 SeptStopPoint:OCETrain TER-8757600 15:340 min—
Tue 29 SeptStopPoint:OCETrain TER-8757600 15:340 min—
Mon 28 SeptStopPoint:OCETrain TER-8757600 15:340 min—
Fri 25 SeptStopPoint:OCETrain TER-8757600 15:350 min—
Thu 24 SeptStopPoint:OCETrain TER-8757600 15:340 min—
Wed 23 SeptStopPoint:OCETrain TER-8757600 15:340 min—