C76 839278 Reims – Laon
Alerts for train 839278
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line C76.
✓ Today’s run finished
Today it reached Laon at 20:27 0 min
- Reims19:41
- Courcy - Brimont19:48
- Aguilcourt - Variscourt19:57
- Guignicourt20:01
- Amifontaine20:07
- Coucy-lès-Eppes20:18
- Laon20:27
Next service: tomorrow 19:41 from Reims · Tue 17 Nov
Last 30 days
Arrival delay at Laon, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 22 Oct Max en route +50 min · last fix heading to Laon +50 min
- Wed 28 Oct Max en route +25 min · last fix heading to Laon +25 min
- Wed 4 Nov Max en route +10 min · last fix heading to Laon +10 min
- Tue 27 Oct Max en route +10 min · last fix heading to Laon +10 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 85% · 23
- 3–10 min 0% · 0
- 10–30 min 11% · 3
- 30+ min 4% · 1
On-time by weekday
- 100% M n=7
- 80% T n=5
- 60% W n=5
- 80% 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 (9 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 19:41 | on time | +10 min | |
| 19:48 / 19:49 | ≈ on time | ≈ +10 min | |
| 19:52 | ≈ on time | ≈ +10 min | |
| 19:57 / 19:58 | ≈ on time | ≈ +10 min | |
| 20:01 / 20:02 | ≈ on time | ≈ +10 min | |
| 20:07 | ≈ on time | ≈ +10 min | |
| 20:12 / 20:13 | ≈ on time | ≈ +10 min | |
| 20:18 / 20:19 | ≈ on time | ≈ +10 min | |
| 20:27 | 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 |
|---|---|---|---|
| Mon 16 Nov | Laon 20:28 | 0 min | — |
| Fri 13 Nov | Laon 20:29 | 0 min | — |
| Thu 12 Nov | Laon 20:28 | 0 min | — |
| Mon 9 Nov | Laon 20:28 | 0 min | — |
| Fri 6 Nov | Laon 20:29 | 0 min | — |
| Thu 5 Nov | Laon 20:29 | No data | — |
| Wed 4 Nov | Laon 20:38 | +10 min | +10 min |
| Tue 3 Nov | Laon 20:29 | 0 min | — |
| Mon 2 Nov | Laon 20:28 | 0 min | — |
| Fri 30 Oct | Laon 20:28 | 0 min | — |
| Thu 29 Oct | Laon 20:28 | 0 min | — |
| Wed 28 Oct | Laon 20:53 | +25 min | +25 min |
| Tue 27 Oct | Laon 20:38 | +10 min | +10 min |
| Mon 26 Oct | Laon 20:29 | 0 min | — |
| Thu 22 Oct | Laon 21:18 | +50 min | +50 min |
| Wed 21 Oct | Laon 20:28 | 0 min | — |
| Tue 20 Oct | Laon 20:28 | 0 min | — |
| Mon 19 Oct | Laon 20:28 | 0 min | — |
| Fri 16 Oct | Laon 20:29 | 0 min | — |
| Thu 15 Oct | Laon 20:29 | 0 min | — |
| Wed 14 Oct | Laon 20:28 | 0 min | — |
| Tue 13 Oct | Laon 20:28 | 0 min | — |
| Mon 12 Oct | Laon 20:28 | 0 min | — |
| Fri 9 Oct | Laon 20:28 | 0 min | +5 min |
| Thu 8 Oct | Laon 20:28 | 0 min | — |
| Wed 7 Oct | Laon 20:28 | 0 min | — |
| Tue 6 Oct | Laon 20:28 | 0 min | — |
| Mon 5 Oct | Laon 20:28 | 0 min | — |