P14 861568 Bourges – Vierzon

View line P14

Bourges 16:08 → Vierzon 16:36 Mon, Tue, Wed, Thu, Fri 0 h 28 min · 6 stops SNCF

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: tomorrow 16:08 from Bourges · Mon 9 Nov

Next departure 16:08 tomorrow · Bourges
On-time · 30 days
79%
15/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
87%
45/52 runs under 3 min
RT coverage: 52 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Thu 29 Oct Max en route +25 min · last fix heading to Vierzon +25 min
  • Wed 19 Aug Max en route +15 min · last fix heading to StopPoint:OCETrain TER-8757611 +15 min
  • 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
  • Mon 19 Oct Max en route +5 min · last fix heading to Vierzon +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 45
  • 3–10 min 8% · 4
  • 10–30 min 6% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=12
  • 92% T n=12
  • 92% W n=12
  • 82% T n=11
  • 60% 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, 52 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:08on time on time
16:14 / 16:15≈ on time ≈ +1 min
16:20 / 16:21≈ on time ≈ +2 min
16:25 / 16:26≈ on time ≈ +3 min
16:30 / 16:31≈ on time ≈ +4 min
16:36on time +5 min

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 NovVierzon 16:370 min—
Thu 5 NovVierzon 16:370 min—
Wed 4 NovVierzon 16:370 min—
Tue 3 NovVierzon 16:380 min—
Mon 2 NovVierzon 16:390 min—
Fri 30 OctVierzon 16:42+5 min+5 min
Thu 29 OctVierzon 17:02+25 min+25 min
Wed 28 OctVierzon 16:370 min—
Tue 27 OctVierzon 16:370 min—
Mon 26 OctVierzon 16:420 min+5 min
Fri 23 OctVierzon 16:48+10 min+10 min
Wed 21 OctVierzon 16:370 min—
Tue 20 OctVierzon 16:370 min—
Mon 19 OctVierzon 16:47+5 min+5 min
Fri 16 OctVierzon 16:370 min—
Thu 15 OctVierzon 16:370 min—
Wed 14 OctVierzon 16:370 min—
Tue 13 OctVierzon 16:370 min—
Mon 12 OctVierzon 16:410 min—
Fri 9 OctVierzon 16:370 min—
Thu 8 OctVierzon 16:370 min—
Wed 7 OctVierzon 16:370 min—
Tue 6 OctVierzon 16:370 min—
Mon 5 OctVierzon 16:420 min—
Thu 1 OctStopPoint:OCETrain TER-8757600 16:350 min—
Wed 30 SeptStopPoint:OCETrain TER-8757600 16:350 min—
Tue 29 SeptStopPoint:OCETrain TER-8757600 16:350 min—
Mon 28 SeptStopPoint:OCETrain TER-8757600 16:390 min—
Thu 24 SeptStopPoint:OCETrain TER-8757609 16:35+5 min+5 min
Wed 23 SeptStopPoint:OCETrain TER-8757600 16:350 min—