P13 882116 Ambérieu-en-Bugey – Mâcon
Alerts for train 882116
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line P13.
It has not run yet today
Last recorded run: Monday 16 November +5 min
Next service: today 17:04 from Ambérieu-en-Bugey · Tue 17 Nov
Last 30 days
Arrival delay at Mâcon, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 4 Nov Max en route +15 min · last fix heading to Mâcon +10 min
- Wed 14 Oct Max en route +10 min · last fix heading to Mâcon +10 min
- Mon 16 Nov Max en route +5 min · last fix heading to Mâcon +5 min
- Fri 13 Nov Max en route +5 min · last fix heading to Mâcon +5 min
- Fri 16 Oct Max en route +5 min · last fix heading to Mâcon +5 min
Distribution · 90 days
19 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 63% · 12
- 3–10 min 26% · 5
- 10–30 min 11% · 2
- 30+ min 0% · 0
On-time by weekday
- 80% M n=5
- 75% T n=4
- 33% W n=3
- 67% T n=3
- 50% F n=4
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 19 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 |
|---|---|---|---|
| 17:04 | on time | +5 min | |
| 17:09 / 17:10 | ≈ on time | ≈ +5 min | |
| 17:13 / 17:14 | ≈ on time | ≈ +5 min | |
| 17:18 / 17:19 | ≈ on time | ≈ +5 min | |
| 17:26 / 17:28 | ≈ on time | ≈ +5 min | |
| 17:33 / 17:34 | ≈ on time | ≈ +5 min | |
| 17:38 / 17:39 | ≈ on time | ≈ +5 min | |
| 17:43 / 17:44 | ≈ on time | ≈ +6 min | |
| 17:49 / 17:50 | ≈ on time | ≈ +6 min | |
| 17:56 | on time | +6 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 | Mâcon 18:03 | +5 min | +5 min |
| Fri 13 Nov | Mâcon 18:03 | +5 min | +5 min |
| Thu 12 Nov | Mâcon 17:57 | 0 min | — |
| Tue 10 Nov | Mâcon 17:57 | 0 min | — |
| Mon 9 Nov | Mâcon 17:57 | 0 min | — |
| Fri 6 Nov | Mâcon 17:57 | 0 min | — |
| Wed 4 Nov | Mâcon 18:07 | +10 min | +15 min |
| Tue 3 Nov | Mâcon 17:58 | 0 min | — |
| Mon 2 Nov | Mâcon 17:57 | 0 min | — |
| Fri 16 Oct | Mâcon 18:02 | +5 min | +5 min |
| Thu 15 Oct | Mâcon 18:02 | +5 min | +5 min |
| Wed 14 Oct | Mâcon 18:07 | +10 min | +10 min |
| Tue 13 Oct | Mâcon 18:02 | +5 min | +5 min |
| Mon 12 Oct | Mâcon 17:57 | 0 min | — |
| Fri 9 Oct | Mâcon 17:57 | 0 min | — |
| Thu 8 Oct | Mâcon 17:58 | 0 min | — |
| Wed 7 Oct | Mâcon 17:57 | 0 min | — |
| Tue 6 Oct | Mâcon 17:57 | 0 min | — |
| Mon 5 Oct | Mâcon 17:57 | 0 min | — |