P14 861555 Vierzon – Bourges

View line P14

Vierzon 07:25 → Bourges 07:53 Mon, Tue, Wed, Thu, Fri, Sat 0 h 28 min · 6 stops SNCF

It does not run today

Last recorded run: Saturday 7 November 0 min

Next service: tomorrow 07:25 from Vierzon · Mon 9 Nov

Next departure 07:25 tomorrow · Vierzon
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
88%
23/26 runs under 3 min
RT coverage: 26 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

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

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

Worst days

  • Tue 3 Nov Max en route +25 min · last fix heading to Bourges +25 min
  • Fri 23 Oct Max en route +5 min · last fix heading to Bourges +5 min
  • Tue 6 Oct Max en route +5 min · last fix heading to Bourges +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 23
  • 3–10 min 8% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 50% T n=4
  • 100% W n=4
  • 100% T n=4
  • 75% F n=4
  • 100% S n=5
  • — S n=0

Stops and timetable

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

Last 90 days, 26 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:25on time on time
07:29 / 07:30≈ on time ≈ on time
07:34 / 07:35≈ on time ≈ +1 min
07:40 / 07:41≈ on time ≈ +1 min
07:46 / 07:47≈ on time ≈ +2 min
07:53on time +3 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
Sat 7 NovBourges 07:540 min—
Wed 4 NovBourges 07:540 min—
Tue 3 NovBourges 08:20+25 min+25 min
Mon 2 NovBourges 07:540 min—
Sat 31 OctBourges 07:540 min—
Fri 30 OctBourges 07:540 min—
Thu 29 OctBourges 07:540 min—
Wed 28 OctBourges 07:540 min—
Tue 27 OctBourges 07:540 min—
Mon 26 OctBourges 07:540 min—
Sat 24 OctBourges 07:540 min—
Fri 23 OctBourges 07:59+5 min+5 min
Thu 22 OctBourges 07:540 min—
Mon 19 OctBourges 07:540 min—
Sat 17 OctBourges 07:540 min—
Fri 16 OctBourges 07:550 min—
Thu 15 OctBourges 07:540 min—
Wed 14 OctBourges 07:540 min—
Tue 13 OctBourges 07:540 min—
Mon 12 OctBourges 07:540 min—
Sat 10 OctBourges 07:540 min—
Fri 9 OctBourges 07:550 min—
Thu 8 OctBourges 07:540 min—
Wed 7 OctBourges 07:550 min—
Tue 6 OctBourges 07:59+5 min+5 min
Mon 5 OctStopPoint:OCETrain TE~7f733cac 07:550 min—