C13 852343 Lisieux – Caen

View line C13

Lisieux 12:04 → Caen 12:37 Mon, Tue, Wed, Thu, Fri 0 h 33 min · 5 stops SNCF

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 12:04 from Lisieux · Tue 17 Nov

Next departure 12:04 today · Lisieux
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 18 full · 0 partial · 2 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 27 full · 1 partial · 2 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

Worst days

  • Thu 22 Oct Max en route +5 min · last fix heading to Caen +5 min
  • Fri 16 Oct Max en route +10 min · last fix heading to Caen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=6
  • 100% W n=5
  • 80% T n=5
  • 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, 28 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
12:04on time on time
12:18 / 12:19≈ on time ≈ on time
12:24 / 12:25≈ on time ≈ on time
12:29 / 12:30≈ on time ≈ on time
12:37on 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
Mon 16 NovCaen 12:390 min—
Fri 13 NovCaen 12:380 min—
Thu 12 NovCaen 12:380 min—
Tue 10 NovCaen 12:380 min—
Mon 9 NovCaen 12:390 min—
Fri 6 NovCaen 12:380 min—
Thu 5 NovCaen 12:38No data—
Wed 4 NovCaen 12:380 min—
Tue 3 NovCaen 12:380 min—
Mon 2 NovCaen 12:380 min—
Fri 30 OctCaen 12:380 min—
Thu 29 OctCaen 12:380 min—
Wed 28 OctCaen 12:380 min—
Tue 27 OctCaen 12:380 min—
Mon 26 OctCaen 12:380 min—
Fri 23 OctCaen 12:38No data—
Thu 22 OctCaen 12:43+5 min+5 min
Wed 21 OctCaen 12:380 min—
Tue 20 OctCaen 12:390 min—
Mon 19 OctCaen 12:380 min—
Fri 16 OctCaen 12:43+5 min+10 min
Thu 15 OctCaen 12:380 min—
Wed 14 OctCaen 12:380 min—
Tue 13 OctCaen 12:380 min—
Mon 12 OctCaen 12:380 min—
Fri 9 OctCaen 12:380 min—
Thu 8 OctCaen 12:380 min—
Wed 7 OctCaen 12:380 min—
Tue 6 OctCaen 12:380 min—
Mon 5 OctStopPoint:OCETrain TE~6431b4fd 12:38Partial coverage0 min—