K5+ 3903 Paris Austerlitz → Bourges

View line K5+

Paris Austerlitz 07:07 → Bourges 09:03 Mon, Tue, Wed, Thu, Fri, Sat 1 h 56 min · 5 stops SNCF

It has not run yet today

Last recorded run: Friday 20 November +15 min

Next service: today 07:07 from Paris Austerlitz · Sat 21 Nov

Next departure 07:07 today · Paris Austerlitz
On-time · 30 days
79%
19/24 runs under 3 min
RT coverage: 24 full · 0 partial · 0 no data
On-time · 90 days
76%
32/42 runs under 3 min
RT coverage: 42 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 26 Sept Max en route +25 min · last fix heading to StopPoint:OCETrain TER-8757600 +25 min
  • Fri 20 Nov Max en route +15 min · last fix heading to Bourges +15 min
  • Tue 17 Nov 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
  • Thu 19 Nov Max en route +5 min · last fix heading to Bourges +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 76% · 32
  • 3–10 min 14% · 6
  • 10–30 min 10% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 86% T n=7
  • 50% W n=6
  • 71% T n=7
  • 71% F n=7
  • 88% S n=8
  • — S n=0

Stops and timetable

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

Last 90 days, 42 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:07on time on time
08:04 / 08:07≈ on time ≈ +2 min
08:30 / 08:32≈ on time ≈ +4 min
08:44 / 08:46≈ on time ≈ +4 min
09:03on 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
Fri 20 NovBourges 09:19+15 min+15 min
Thu 19 NovBourges 09:09+5 min+5 min
Wed 18 NovBourges 09:040 min—
Tue 17 NovBourges 09:14+10 min+10 min
Mon 16 NovBourges 09:040 min—
Sat 14 NovBourges 09:040 min—
Fri 13 NovBourges 09:040 min—
Thu 12 NovBourges 09:040 min—
Tue 10 NovBourges 09:040 min—
Mon 9 NovBourges 09:040 min—
Sat 7 NovBourges 09:040 min—
Fri 6 NovBourges 09:040 min—
Thu 5 NovBourges 09:040 min—
Wed 4 NovBourges 09:040 min—
Tue 3 NovBourges 09:040 min+5 min
Mon 2 NovBourges 09:040 min—
Sat 31 OctBourges 09:050 min—
Fri 30 OctBourges 09:040 min—
Thu 29 OctBourges 09:040 min—
Wed 28 OctBourges 09:040 min—
Tue 27 OctBourges 09:040 min—
Mon 26 OctBourges 09:09+5 min+5 min
Sat 24 OctBourges 09:040 min—
Fri 23 OctBourges 09:09+5 min+5 min
Thu 22 OctBourges 09:09+5 min+5 min
Wed 21 OctBourges 09:09+5 min+5 min
Tue 20 OctBourges 09:040 min—
Mon 19 OctBourges 09:040 min—
Sat 17 OctBourges 09:040 min—
Fri 16 OctBourges 09:040 min—