K39 853728 Caen – Alençon
Alerts for train 853728
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 has not run yet today
Last recorded run: Thursday 5 November No data
Next service: today 20:09 from Caen · Fri 6 Nov
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 2 Nov Max en route +80 min · last fix heading to Alençon +80 min
- Tue 13 Oct Max en route +20 min · last fix heading to Alençon +20 min
- Wed 14 Oct Max en route +25 min · last fix heading to Alençon +15 min
- Wed 21 Oct Max en route +5 min · last fix heading to Alençon +5 min
- Mon 19 Oct Max en route +5 min · last fix heading to Alençon +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 77% · 17
- 3–10 min 9% · 2
- 10–30 min 9% · 2
- 30+ min 5% · 1
On-time by weekday
- 60% M n=5
- 80% T n=5
- 60% W n=5
- 100% T n=4
- 100% F n=3
- — 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 |
|---|---|---|---|
| 20:09 | on time | on time | |
| 20:22 / 20:23 | ≈ on time | ≈ +11 min | |
| 20:28 / 20:29 | ≈ on time | ≈ +12 min | |
| 20:48 / 20:50 | ≈ on time | ≈ +14 min | |
| 20:58 / 20:59 | ≈ on time | ≈ +14 min | |
| 21:06 / 21:07 | ≈ on time | ≈ +14 min | |
| 21:20 | on time | +14 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 |
|---|---|---|---|
| Thu 5 Nov | Alençon 21:19 | No data | — |
| Wed 4 Nov | Alençon 21:19 | 0 min | — |
| Tue 3 Nov | Alençon 21:22 | 0 min | — |
| Mon 2 Nov | Alençon 22:39 | +80 min | +80 min |
| Fri 30 Oct | Alençon 21:21 | 0 min | — |
| Thu 29 Oct | Alençon 21:21 | 0 min | +5 min |
| Wed 28 Oct | Alençon 21:21 | 0 min | +5 min |
| Tue 27 Oct | Alençon 21:21 | 0 min | — |
| Mon 26 Oct | Alençon 21:22 | 0 min | — |
| Fri 23 Oct | Alençon 21:22 | No data | — |
| Thu 22 Oct | Alençon 21:21 | 0 min | — |
| Wed 21 Oct | Alençon 21:26 | +5 min | +5 min |
| Tue 20 Oct | Alençon 21:21 | 0 min | — |
| Mon 19 Oct | Alençon 21:26 | +5 min | +5 min |
| Fri 16 Oct | Alençon 21:21 | 0 min | — |
| Thu 15 Oct | Alençon 21:21 | 0 min | — |
| Wed 14 Oct | Alençon 21:36 | +15 min | +25 min |
| Tue 13 Oct | Alençon 21:41 | +20 min | +20 min |
| Mon 12 Oct | Alençon 21:21 | 0 min | — |
| Fri 9 Oct | Alençon 21:21 | 0 min | — |
| Thu 8 Oct | Alençon 21:22 | 0 min | — |
| Wed 7 Oct | Alençon 21:21 | 0 min | — |
| Tue 6 Oct | Alençon 21:21 | 0 min | — |
| Mon 5 Oct | Alençon 21:21 | 0 min | — |