P14 861577 Vierzon – Bourges

View line P14

Vierzon 18:28 → Bourges 18:56 Daily 0 h 28 min · 6 stops SNCF

It has not run yet today

Last recorded run: Saturday 7 November +25 min

Next service: today 18:28 from Vierzon · Sun 8 Nov

Next departure 18:28 today · Vierzon
On-time · 30 days
93%
26/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
On-time · 90 days
89%
73/82 runs under 3 min
RT coverage: 82 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: 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

  • Fri 14 Aug Max en route +30 min · last fix heading to StopPoint:OCETrain TER-8757600 +30 min
  • Sat 7 Nov Max en route +25 min · last fix heading to Bourges +25 min
  • Sat 3 Oct Max en route +40 min · last fix heading to StopPoint:OCETrain TER-8757611 +15 min
  • Fri 23 Oct Max en route +10 min · last fix heading to Bourges +10 min
  • Tue 11 Aug Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8757613 +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 73
  • 3–10 min 5% · 4
  • 10–30 min 5% · 4
  • 30+ min 1% · 1

On-time by weekday

  • 100% M n=11
  • 83% T n=12
  • 100% W n=12
  • 100% T n=11
  • 82% F n=11
  • 85% S n=13
  • 75% S n=12

Stops and timetable

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

Last 90 days, 82 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
18:28on time on time
18:32 / 18:33≈ on time ≈ +1 min
18:37 / 18:38≈ on time ≈ +1 min
18:43 / 18:44≈ on time ≈ +2 min
18:49 / 18:50≈ on time ≈ +3 min
18:56on 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 19:22+25 min+25 min
Fri 6 NovBourges 18:570 min—
Wed 4 NovBourges 18:570 min—
Tue 3 NovBourges 18:580 min—
Mon 2 NovBourges 18:570 min—
Sun 1 NovBourges 18:570 min—
Sat 31 OctBourges 18:580 min—
Fri 30 OctBourges 18:570 min—
Thu 29 OctBourges 18:570 min—
Wed 28 OctBourges 18:570 min—
Tue 27 OctBourges 18:570 min—
Mon 26 OctBourges 18:580 min—
Sun 25 OctBourges 18:570 min—
Sat 24 OctBourges 18:570 min—
Fri 23 OctBourges 19:08+10 min+10 min
Thu 22 OctBourges 18:580 min—
Wed 21 OctBourges 18:570 min—
Tue 20 OctBourges 18:570 min—
Mon 19 OctBourges 18:570 min—
Sun 18 OctBourges 18:570 min—
Sat 17 OctBourges 18:580 min—
Fri 16 OctBourges 18:570 min—
Thu 15 OctBourges 18:570 min—
Wed 14 OctBourges 18:570 min—
Tue 13 OctBourges 18:570 min—
Mon 12 OctBourges 18:570 min—
Sun 11 OctBourges 18:570 min—
Sat 10 OctBourges 18:580 min—
Fri 9 OctBourges 18:570 min—
Thu 8 OctBourges 18:570 min—