P14 861557 Vierzon – Bourges

View line P14

Vierzon 08:28 → Bourges 08:55 Mon, Tue, Wed, Thu, Fri, Sat 0 h 27 min · 6 stops SNCF

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 08:28 from Vierzon · Mon 9 Nov

Next departure 08:28 today · Vierzon
On-time · 30 days
68%
15/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
75%
21/28 runs under 3 min
RT coverage: 28 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

  • Wed 28 Oct Max en route +10 min · last fix heading to Bourges +10 min
  • Thu 29 Oct Max en route +5 min · last fix heading to Bourges +5 min
  • Tue 27 Oct Max en route +5 min · last fix heading to Bourges +5 min
  • Mon 26 Oct Max en route +5 min · last fix heading to Bourges +5 min
  • Thu 22 Oct Max en route +5 min · last fix heading to Bourges +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 21
  • 3–10 min 21% · 6
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
08:28on time +5 min
08:32 / 08:33≈ on time ≈ +5 min
08:37 / 08:38≈ on time ≈ +5 min
08:42 / 08:43≈ on time ≈ +5 min
08:48 / 08:49≈ on time ≈ +5 min
08:55on 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
Sat 7 NovBourges 08:540 min—
Fri 6 NovBourges 08:570 min—
Wed 4 NovBourges 08:570 min—
Mon 2 NovBourges 08:570 min—
Sat 31 OctBourges 08:560 min—
Fri 30 OctBourges 08:570 min—
Thu 29 OctBourges 09:02+5 min+5 min
Wed 28 OctBourges 09:07+10 min+10 min
Tue 27 OctBourges 09:02+5 min+5 min
Mon 26 OctBourges 09:02+5 min+5 min
Sat 24 OctBourges 08:560 min—
Fri 23 OctBourges 08:570 min—
Thu 22 OctBourges 09:02+5 min+5 min
Wed 21 OctBourges 09:02+5 min+5 min
Tue 20 OctBourges 08:570 min—
Mon 19 OctBourges 08:570 min—
Sat 17 OctBourges 09:01+5 min+5 min
Fri 16 OctBourges 08:570 min—
Thu 15 OctBourges 08:570 min—
Wed 14 OctBourges 08:570 min—
Tue 13 OctBourges 08:570 min—
Mon 12 OctBourges 08:580 min—
Sat 10 OctBourges 08:560 min—
Fri 9 OctBourges 08:580 min—
Thu 8 OctBourges 08:570 min—
Wed 7 OctBourges 08:580 min—
Tue 6 OctBourges 08:570 min—
Mon 5 OctStopPoint:OCETrain TE~7f733cac 08:580 min—