C13 852357 Lisieux – Caen

View line C13

Lisieux 19:06 → Caen 19:39 Mon, Tue, Wed, Thu, Fri 0 h 33 min · 5 stops SNCF

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 19:06 from Lisieux · Mon 16 Nov

Next departure 19:06 today · Lisieux
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 17 full · 0 partial · 2 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 27 full · 0 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: +2 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

  • Mon 9 Nov Max en route +50 min · last fix heading to Caen +45 min
  • Mon 19 Oct Max en route +5 min · last fix heading to Caen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 4% · 1

On-time by weekday

  • 67% M n=6
  • 100% T n=6
  • 100% W n=5
  • 100% T n=5
  • 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, 27 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:06on time on time
19:20 / 19:21≈ on time ≈ on time
19:26 / 19:27≈ on time ≈ on time
19:31 / 19:32≈ on time ≈ on time
19:39on 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 19:390 min—
Thu 12 NovCaen 19:390 min—
Tue 10 NovCaen 19:390 min—
Mon 9 NovCaen 20:19+45 min+50 min
Fri 6 NovCaen 19:400 min—
Thu 5 NovCaen 19:39No data—
Wed 4 NovCaen 19:390 min—
Tue 3 NovCaen 19:390 min—
Mon 2 NovCaen 19:390 min—
Fri 30 OctCaen 19:400 min—
Thu 29 OctCaen 19:400 min—
Wed 28 OctCaen 19:400 min—
Tue 27 OctCaen 19:400 min+5 min
Mon 26 OctCaen 19:410 min—
Fri 23 OctCaen 19:41No data—
Thu 22 OctCaen 19:400 min—
Wed 21 OctCaen 19:400 min—
Tue 20 OctCaen 19:400 min—
Mon 19 OctCaen 19:45+5 min+5 min
Fri 16 OctCaen 19:400 min—
Thu 15 OctCaen 19:400 min—
Wed 14 OctCaen 19:400 min—
Tue 13 OctCaen 19:410 min—
Mon 12 OctCaen 19:400 min—
Fri 9 OctCaen 19:400 min—
Thu 8 OctCaen 19:400 min—
Wed 7 OctCaen 19:400 min—
Tue 6 OctCaen 19:400 min—
Mon 5 OctCaen 19:380 min—