P14 861569 Vierzon – Bourges

View line P14

Vierzon 14:22 → Bourges 14:51 Daily 0 h 29 min · 6 stops SNCF

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 14:22 from Vierzon · Mon 9 Nov

Next departure 14:22 today · Vierzon
On-time · 30 days
78%
21/27 runs under 3 min
RT coverage: 27 full · 0 partial · 0 no data
On-time · 90 days
78%
62/79 runs under 3 min
RT coverage: 79 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: +5 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

  • Sat 7 Nov Max en route +25 min · last fix heading to Bourges +25 min
  • Sun 11 Oct Max en route +15 min · last fix heading to Bourges +15 min
  • Mon 14 Sept Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8757613 +10 min
  • Sat 12 Sept Max en route +40 min · last fix heading to StopPoint:OCETrain TER-8757613 +10 min
  • Thu 27 Aug Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8757613 +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 62
  • 3–10 min 15% · 12
  • 10–30 min 6% · 5
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=12
  • 83% T n=12
  • 92% W n=13
  • 73% T n=11
  • 60% F n=5
  • 69% S n=13
  • 92% S n=13

Stops and timetable

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

Last 90 days, 79 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
14:22on time on time
14:26 / 14:27≈ on time ≈ +1 min
14:31 / 14:32≈ on time ≈ +2 min
14:37 / 14:38≈ on time ≈ +3 min
14:43 / 14:44≈ on time ≈ +4 min
14:51on 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
Sun 8 NovBourges 14:520 min—
Sat 7 NovBourges 15:17+25 min+25 min
Fri 6 NovBourges 14:520 min—
Wed 4 NovBourges 14:520 min—
Tue 3 NovBourges 14:530 min—
Mon 2 NovBourges 14:520 min—
Sun 1 NovBourges 14:520 min—
Sat 31 OctBourges 14:520 min—
Fri 30 OctBourges 14:520 min—
Wed 28 OctBourges 14:520 min—
Tue 27 OctBourges 14:57+5 min+10 min
Mon 26 OctBourges 14:58+5 min+5 min
Sun 25 OctBourges 14:520 min—
Sat 24 OctBourges 14:520 min—
Fri 23 OctBourges 14:57+5 min+5 min
Thu 22 OctBourges 14:520 min—
Wed 21 OctBourges 14:520 min—
Tue 20 OctBourges 14:520 min—
Mon 19 OctBourges 14:530 min—
Sun 18 OctBourges 14:520 min—
Sat 17 OctBourges 14:520 min—
Fri 16 OctBourges 14:57+5 min+5 min
Thu 15 OctBourges 14:520 min—
Wed 14 OctBourges 14:530 min—
Tue 13 OctBourges 14:520 min—
Mon 12 OctBourges 14:520 min—
Sun 11 OctBourges 15:07+15 min+15 min
Sat 10 OctBourges 14:530 min—
Fri 9 OctBourges 14:520 min—
Thu 8 OctBourges 14:520 min—