K39 16586 Tours – Caen

View line K39

Tours 19:11 → Caen 22:00 Wed, Sun 2 h 49 min · 9 stops SNCF

It does not run today

Last recorded run: Sunday 1 November 0 min

Next service: tomorrow 19:11 from Tours · Sun 8 Nov

Next departure 19:11 tomorrow · Tours
On-time · 30 days
75%
3/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
89%
8/9 runs under 3 min
RT coverage: 9 full · 0 partial · 8 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Caen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 18 Oct Max en route +5 min · last fix heading to Caen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 8
  • 3–10 min 11% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • — S n=0
  • 89% S n=9

Stops and timetable

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

Last 90 days, 9 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
19:11on time on time
19:41 / 19:42≈ on time ≈ on time
20:11 / 20:15≈ on time ≈ on time
20:49 / 20:52≈ on time ≈ +1 min
21:05 / 21:06≈ on time ≈ +1 min
21:19 / 21:21≈ on time ≈ +1 min
21:40 / 21:41≈ on time ≈ +1 min
21:46 / 21:47≈ on time ≈ +1 min
22:00on time +1 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 1 NovCaen 21:590 min—
Sun 25 OctCaen 22:010 min+30 min
Sun 18 OctCaen 22:06+5 min+5 min
Sun 11 OctCaen 22:010 min—
Sun 4 OctStopPoint:OCETrain TE~6431b4fd 22:010 min—
Wed 30 SeptStopPoint:OCETrain TER-8744400 21:59No data—
Wed 23 SeptStopPoint:OCETrain TER-8744400 21:59No data—
Wed 16 SeptStopPoint:OCETrain TER-8744400 21:59No data—
Sun 13 SeptStopPoint:OCETrain TER-8744400 21:590 min+5 min
Wed 9 SeptStopPoint:OCETrain TER-8744400 21:59No data—
Sun 6 SeptStopPoint:OCETrain TER-8744400 21:590 min—
Wed 2 SeptStopPoint:OCETrain TER-8744400 21:59No data—
Sun 30 AugStopPoint:OCETrain TER-8744400 21:590 min—
Wed 26 AugStopPoint:OCETrain TER-8744400 21:59No data—
Wed 19 AugStopPoint:OCETrain TER-8744400 21:59No data—
Sun 16 AugStopPoint:OCETrain TER-8744400 21:590 min—
Wed 12 AugStopPoint:OCETrain TER-8744400 21:59No data—