K39 853630 Caen – Alençon

View line K39

Caen 11:15 → Alençon 12:31 Mon, Tue, Wed, Thu, Fri 1 h 16 min · 7 stops SNCF

It has not run yet today

Last recorded run: Thursday 12 November +10 min

Next service: today 11:15 from Caen · Fri 13 Nov

Next departure 11:15 today · Caen
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 17 full · 1 partial · 2 no data
On-time · 90 days
81%
21/26 runs under 3 min
RT coverage: 25 full · 1 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+23min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Alençon, 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 5 Oct Max en route +110 min · last fix heading to Alençon +110 min
  • Thu 15 Oct Max en route +70 min · last fix heading to Alençon +55 min
  • Wed 14 Oct Max en route +35 min · last fix heading to Alençon +35 min
  • Thu 12 Nov Max en route +10 min · last fix heading to Caen +10 min
  • Wed 7 Oct Max en route +20 min · last fix heading to Alençon +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 21
  • 3–10 min 0% · 0
  • 10–30 min 8% · 2
  • 30+ min 12% · 3

On-time by weekday

  • 83% M n=6
  • 100% T n=6
  • 60% W n=5
  • 60% T n=5
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 26 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:15on time +5 min
11:28 / 11:29≈ on time ≈ +4 min
11:35 / 11:36≈ on time ≈ +7 min
11:55 / 11:57≈ on time ≈ +13 min
12:06 / 12:07≈ on time ≈ +17 min
12:15 / 12:16≈ on time ≈ +20 min
12:31on 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 12 NovCaen 11:24Partial coverage+10 min+10 min
Tue 10 NovAlençon 12:320 min—
Mon 9 NovAlençon 12:330 min—
Fri 6 NovAlençon 12:320 min—
Thu 5 NovAlençon 12:32No data—
Wed 4 NovAlençon 12:320 min—
Tue 3 NovAlençon 12:330 min—
Mon 2 NovAlençon 12:320 min—
Fri 30 OctAlençon 12:320 min—
Thu 29 OctAlençon 12:320 min—
Wed 28 OctAlençon 12:320 min—
Tue 27 OctAlençon 12:320 min—
Mon 26 OctAlençon 12:320 min—
Fri 23 OctAlençon 12:32No data—
Thu 22 OctAlençon 12:320 min—
Wed 21 OctAlençon 12:320 min—
Tue 20 OctAlençon 12:330 min—
Mon 19 OctAlençon 12:320 min—
Fri 16 OctAlençon 12:320 min—
Thu 15 OctAlençon 13:27+55 min+70 min
Wed 14 OctAlençon 13:07+35 min+35 min
Tue 13 OctAlençon 12:320 min—
Mon 12 OctAlençon 12:330 min—
Fri 9 OctAlençon 12:320 min—
Thu 8 OctAlençon 12:320 min—
Wed 7 OctAlençon 12:42+10 min+20 min
Tue 6 OctAlençon 12:320 min—
Mon 5 OctAlençon 14:30+110 min+110 min