C12 852632 Coutances → Caen

View line C12

Coutances 16:41 → Caen 17:48 Mon, Tue, Wed, Thu, Fri 1 h 07 min · 5 stops SNCF

TER 852632 Coutances–Caen: final delay under 3 min on 11 of its 16 runs with data in the last 30 days (69%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 06:55 (GMT+1).

It does not run today

Last recorded run: Friday 20 November +5 min

Next service: tomorrow 16:41 from Coutances · Mon 23 Nov

Next departure 16:41 tomorrow · Coutances
On-time · 30 days
69%
11/16 runs under 3 min
RT coverage: 16 full · 0 partial · 1 no data
On-time · 90 days
79%
26/33 runs under 3 min
RT coverage: 33 full · 0 partial · 2 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 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

  • Tue 17 Nov Max en route +15 min · last fix heading to Caen +15 min
  • Fri 20 Nov Max en route +5 min · last fix heading to Caen +5 min
  • Mon 16 Nov Max en route +5 min · last fix heading to Caen +5 min
  • Thu 12 Nov Max en route +5 min · last fix heading to Caen +5 min
  • Tue 27 Oct Max en route +5 min · last fix heading to Caen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 26
  • 3–10 min 18% · 6
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 75% T n=8
  • 83% W n=6
  • 71% T n=7
  • 80% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 33 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:41on time on time
17:02 / 17:04≈ on time ≈ +2 min
17:16 / 17:17≈ on time ≈ +3 min
17:30 / 17:31≈ on time ≈ +4 min
17:48on 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 NovCaen 17:54+5 min+5 min
Thu 19 NovCaen 17:490 min—
Wed 18 NovCaen 17:490 min—
Tue 17 NovCaen 18:04+15 min+15 min
Mon 16 NovCaen 17:54+5 min+5 min
Fri 13 NovCaen 17:500 min—
Thu 12 NovCaen 17:54+5 min+5 min
Tue 10 NovCaen 17:490 min+5 min
Mon 9 NovCaen 17:490 min—
Fri 6 NovCaen 17:490 min—
Thu 5 NovCaen 17:49No data—
Tue 3 NovCaen 17:490 min—
Mon 2 NovCaen 17:490 min—
Thu 29 OctCaen 17:490 min+5 min
Wed 28 OctCaen 17:490 min—
Tue 27 OctCaen 17:54+5 min+5 min
Mon 26 OctCaen 17:500 min—
Fri 23 OctCaen 17:50No data—
Thu 22 OctCaen 17:55+5 min+5 min
Wed 21 OctCaen 17:500 min—
Tue 20 OctCaen 17:490 min—
Mon 19 OctCaen 17:490 min—
Fri 16 OctCaen 17:490 min—
Thu 15 OctCaen 17:490 min—
Wed 14 OctCaen 17:490 min—
Tue 13 OctCaen 17:490 min—
Mon 12 OctCaen 17:490 min—
Fri 9 OctCaen 17:490 min—
Thu 8 OctCaen 17:500 min—
Wed 7 OctCaen 17:490 min—