C13 852341 Lisieux – Caen

View line C13

Lisieux 11:02 → Caen 11:34 Mon, Tue, Wed, Thu, Fri 0 h 32 min · 5 stops SNCF

It does not run today

Last recorded run: Friday 13 November 0 min

Next service: tomorrow 11:02 from Lisieux · Mon 16 Nov

Next departure 11:02 tomorrow · Lisieux
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 18 full · 0 partial · 1 no data
On-time · 90 days
100%
42/42 runs under 3 min
RT coverage: 42 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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 100% · 42
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=11
  • 100% W n=9
  • 100% T n=10
  • 100% 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, 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
11:02on time on time
11:15 / 11:16≈ on time ≈ on time
11:21 / 11:22≈ on time ≈ on time
11:26 / 11:27≈ on time ≈ on time
11:34on time on time

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 13 NovCaen 11:340 min—
Thu 12 NovCaen 11:340 min—
Tue 10 NovCaen 11:340 min—
Mon 9 NovCaen 11:340 min—
Fri 6 NovCaen 11:340 min—
Thu 5 NovCaen 11:340 min—
Wed 4 NovCaen 11:340 min—
Tue 3 NovCaen 11:340 min—
Mon 2 NovCaen 11:340 min—
Fri 30 OctCaen 11:350 min—
Thu 29 OctCaen 11:350 min—
Wed 28 OctCaen 11:350 min—
Tue 27 OctCaen 11:350 min—
Mon 26 OctCaen 11:350 min—
Fri 23 OctCaen 11:35No data—
Thu 22 OctCaen 11:350 min—
Wed 21 OctCaen 11:350 min—
Tue 20 OctCaen 11:360 min—
Mon 19 OctCaen 11:350 min—
Fri 16 OctCaen 11:350 min—
Thu 15 OctCaen 11:350 min+5 min
Wed 14 OctCaen 11:350 min—
Tue 13 OctCaen 11:350 min—
Mon 12 OctCaen 11:360 min—
Fri 9 OctCaen 11:360 min—
Thu 8 OctCaen 11:350 min—
Wed 7 OctCaen 11:350 min—
Tue 6 OctCaen 11:350 min—
Mon 5 OctStopPoint:OCETrain TE~6431b4fd 11:350 min—
Tue 29 SeptStopPoint:OCETrain TER-8744400 11:330 min—