K39 853703 Alençon – Caen
Alerts for train 853703
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line K39.
✓ Today’s run finished
Today it reached Caen at 07:05 +5 min
- Alençon05:50
- Sées06:01
- Surdon06:09
- Argentan06:18
- Saint-Pierre-sur-Dives06:39
- Mézidon - Canon06:45
- Caen07:00
Next service: Monday 05:50 from Alençon · Mon 16 Nov
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 26 Oct Max en route +30 min · last fix heading to Caen +30 min
- Mon 2 Nov Max en route +25 min · last fix heading to Caen +25 min
- Tue 10 Nov Max en route +10 min · last fix heading to Caen +10 min
- Wed 28 Oct Max en route +10 min · last fix heading to Caen +10 min
- Fri 13 Nov Max en route +5 min · last fix heading to Caen +5 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 73% · 19
- 3–10 min 12% · 3
- 10–30 min 12% · 3
- 30+ min 4% · 1
On-time by weekday
- 67% M n=6
- 67% T n=6
- 75% W n=4
- 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 (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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 05:50 | on time | on time | |
| 06:01 / 06:02 | ≈ on time | ≈ +2 min | |
| 06:09 / 06:10 | ≈ on time | ≈ +3 min | |
| 06:18 / 06:20 | ≈ on time | ≈ +4 min | |
| 06:39 / 06:40 | ≈ on time | ≈ +7 min | |
| 06:45 / 06:46 | ≈ on time | ≈ +8 min | |
| 07:00 | on time | +10 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 13 Nov | Caen 07:04 | +5 min | +5 min |
| Thu 12 Nov | Caen 06:59 | 0 min | — |
| Tue 10 Nov | Caen 07:09 | +10 min | +10 min |
| Mon 9 Nov | Caen 06:59 | 0 min | — |
| Fri 6 Nov | Caen 07:02 | 0 min | — |
| Thu 5 Nov | Caen 06:59 | No data | — |
| Tue 3 Nov | Caen 07:04 | +5 min | +5 min |
| Mon 2 Nov | Caen 07:24 | +25 min | +25 min |
| Fri 30 Oct | Caen 07:01 | 0 min | — |
| Thu 29 Oct | Caen 07:01 | 0 min | — |
| Wed 28 Oct | Caen 07:11 | +10 min | +10 min |
| Tue 27 Oct | Caen 07:01 | 0 min | — |
| Mon 26 Oct | Caen 07:29 | +30 min | +30 min |
| Fri 23 Oct | Caen 07:01 | No data | — |
| Thu 22 Oct | Caen 07:06 | +5 min | +5 min |
| Wed 21 Oct | Caen 07:01 | 0 min | — |
| Tue 20 Oct | Caen 07:01 | 0 min | — |
| Mon 19 Oct | Caen 06:59 | 0 min | — |
| Fri 16 Oct | Caen 07:01 | 0 min | — |
| Thu 15 Oct | Caen 07:02 | 0 min | — |
| Wed 14 Oct | Caen 07:01 | 0 min | — |
| Tue 13 Oct | Caen 07:01 | 0 min | — |
| Mon 12 Oct | Caen 06:59 | 0 min | — |
| Fri 9 Oct | Caen 07:02 | 0 min | — |
| Thu 8 Oct | Caen 07:01 | 0 min | — |
| Wed 7 Oct | Caen 07:02 | 0 min | +5 min |
| Tue 6 Oct | Caen 07:02 | 0 min | — |
| Mon 5 Oct | StopPoint:OCETrain TE~6431b4fd 07:02 | 0 min | — |