C12 852615 Caen – Coutances

View line C12

Caen 08:11 → Coutances 09:25 Mon, Tue, Wed, Thu, Fri 1 h 14 min · 8 stops SNCF

✓ Today’s run finished

Today, last fix heading to Coutances at 09:24 No data

  1. Caen08:11
  2. Bretteville - Norrey08:19
  3. Audrieu08:25
  4. Le Molay-Littry08:41
  5. Lison08:49
  6. Saint-Lô09:02
  7. Coutances09:25

Next service: tomorrow 08:11 from Caen · Fri 6 Nov

Next departure 08:11 tomorrow · Caen
On-time · 30 days
78%
14/18 runs under 3 min
RT coverage: 18 full · 0 partial · 2 no data
On-time · 90 days
75%
15/20 runs under 3 min
RT coverage: 20 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+25min
9 in 10 runs arrive with less than this
30 days: +22 min

Last 30 days

Arrival delay at Coutances, 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 2 Nov Max en route +45 min · last fix heading to Coutances +45 min
  • Mon 26 Oct Max en route +25 min · last fix heading to Coutances +25 min
  • Mon 5 Oct Max en route +25 min · last fix heading to StopPoint:OCETrain TE~c3a08838 +25 min
  • Mon 12 Oct Max en route +20 min · last fix heading to Coutances +20 min
  • Wed 28 Oct Max en route +10 min · last fix heading to Coutances +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 15
  • 3–10 min 0% · 0
  • 10–30 min 20% · 4
  • 30+ min 5% · 1

On-time by weekday

  • 20% M n=5
  • 100% T n=3
  • 80% W n=5
  • 100% T n=4
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 20 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:11on time +16 min
08:19 / 08:20≈ on time ≈ +16 min
08:25 / 08:26≈ on time ≈ +17 min
08:32 / 08:33≈ on time ≈ +18 min
08:41 / 08:42≈ on time ≈ +19 min
08:49 / 08:50≈ on time ≈ +20 min
09:02 / 09:04≈ on time ≈ +20 min
09:25on time +25 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
Thu 5 NovCoutances 09:24No data—
Wed 4 NovCoutances 09:240 min—
Mon 2 NovCoutances 10:09+45 min+45 min
Fri 30 OctCoutances 09:260 min—
Thu 29 OctCoutances 09:260 min—
Wed 28 OctCoutances 09:36+10 min+10 min
Mon 26 OctCoutances 09:51+25 min+25 min
Fri 23 OctCoutances 09:26No data—
Thu 22 OctCoutances 09:260 min—
Wed 21 OctCoutances 09:260 min—
Tue 20 OctCoutances 09:260 min—
Mon 19 OctCoutances 09:260 min—
Fri 16 OctCoutances 09:260 min—
Thu 15 OctCoutances 09:260 min—
Wed 14 OctCoutances 09:260 min—
Tue 13 OctCoutances 09:260 min—
Mon 12 OctCoutances 09:47+20 min+20 min
Fri 9 OctCoutances 09:270 min—
Thu 8 OctCoutances 09:260 min—
Wed 7 OctCoutances 09:270 min—
Tue 6 OctCoutances 09:260 min—
Mon 5 OctStopPoint:OCETrain TE~c3a08838 09:52+25 min+25 min