K39 853603 Alençon – Caen
Alerts for train 853603
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.
It does not run today
Last recorded run: Friday 13 November +15 min
Next service: Tuesday 06:51 from Alençon · Tue 17 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
- Fri 13 Nov Max en route +15 min · last fix heading to Caen +15 min
- Tue 10 Nov Max en route +20 min · last fix heading to Caen +15 min
- Thu 5 Nov Max en route +10 min · last fix heading to Caen +10 min
- Thu 29 Oct Max en route +10 min · last fix heading to Caen +10 min
- Fri 6 Nov Max en route +5 min · last fix heading to Caen +5 min
Distribution · 90 days
22 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 68% · 15
- 3–10 min 14% · 3
- 10–30 min 18% · 4
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- 67% T n=6
- 80% W n=5
- 67% T n=6
- 60% 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, 22 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 |
|---|---|---|---|
| 06:51 | on time | on time | |
| 07:03 / 07:04 | ≈ on time | ≈ +2 min | |
| 07:11 / 07:12 | ≈ on time | ≈ +3 min | |
| 07:20 / 07:22 | ≈ on time | ≈ +4 min | |
| 07:41 / 07:42 | ≈ on time | ≈ +7 min | |
| 07:47 / 07:48 | ≈ on time | ≈ +8 min | |
| 08:02 | 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 08:18 | +15 min | +15 min |
| Thu 12 Nov | Caen 08:03 | 0 min | — |
| Tue 10 Nov | Caen 08:18 | +15 min | +20 min |
| Fri 6 Nov | Caen 08:08 | +5 min | +5 min |
| Thu 5 Nov | Caen 08:13 | +10 min | +10 min |
| Wed 4 Nov | Caen 08:03 | 0 min | — |
| Tue 3 Nov | Caen 08:03 | 0 min | — |
| Fri 30 Oct | Caen 08:03 | 0 min | — |
| Thu 29 Oct | Caen 08:13 | +10 min | +10 min |
| Wed 28 Oct | Caen 08:08 | +5 min | +5 min |
| Tue 27 Oct | Caen 08:03 | 0 min | — |
| Fri 23 Oct | Caen 08:03 | No data | — |
| Thu 22 Oct | Caen 08:03 | 0 min | +5 min |
| Wed 21 Oct | Caen 08:03 | 0 min | — |
| Tue 20 Oct | Caen 08:08 | +5 min | +5 min |
| Fri 16 Oct | Caen 08:04 | 0 min | — |
| Thu 15 Oct | Caen 08:03 | 0 min | — |
| Wed 14 Oct | Caen 08:03 | 0 min | — |
| Tue 13 Oct | Caen 08:03 | 0 min | — |
| Fri 9 Oct | Caen 08:03 | 0 min | — |
| Thu 8 Oct | Caen 08:03 | 0 min | — |
| Wed 7 Oct | Caen 08:04 | 0 min | — |
| Tue 6 Oct | Caen 08:03 | 0 min | — |