P14 861573 Vierzon – Bourges

View line P14

Vierzon 16:24 → Bourges 16:52 Daily 0 h 28 min · 6 stops SNCF

✓ Today’s run finished

Today it reached Bourges at 16:52 0 min

  1. Vierzon16:24
  2. Vierzon Forges16:28
  3. Foëcy16:33
  4. Mehun-sur-Yèvre16:38
  5. Marmagne16:44
  6. Bourges16:52

Next service: tomorrow 16:24 from Vierzon · Sun 8 Nov

Next departure 16:24 tomorrow · Vierzon
On-time · 30 days
75%
21/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
On-time · 90 days
72%
23/32 runs under 3 min
RT coverage: 32 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+10min
9 in 10 runs arrive with less than this
30 days: +7 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

  • Mon 19 Oct Max en route +25 min · last fix heading to Bourges +25 min
  • Sat 17 Oct Max en route +20 min · last fix heading to Bourges +20 min
  • Mon 5 Oct Max en route +15 min · last fix heading to Bourges +15 min
  • Tue 20 Oct Max en route +10 min · last fix heading to Bourges +10 min
  • Wed 7 Oct Max en route +10 min · last fix heading to Bourges +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 72% · 23
  • 3–10 min 13% · 4
  • 10–30 min 16% · 5
  • 30+ min 0% · 0

On-time by weekday

  • 40% M n=5
  • 80% T n=5
  • 60% W n=5
  • 75% T n=4
  • 100% F n=5
  • 75% S n=4
  • 75% S n=4

Stops and timetable

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

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