F32 865482 Niversac – Mussidan
Alerts for train 865482
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line F32.
It has not run yet today
Last recorded run: Wednesday 4 November +5 min
Next service: today 16:29 from Niversac · Thu 5 Nov
Last 30 days
Arrival delay at Mussidan, 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 16 Oct Max en route +10 min · last fix heading to Mussidan +10 min
- Wed 4 Nov Max en route +5 min · last fix heading to Mussidan +5 min
- Mon 26 Oct Max en route +5 min · last fix heading to Mussidan +5 min
- Wed 21 Oct Max en route +5 min · last fix heading to Mussidan +5 min
- Wed 7 Oct Max en route +5 min · last fix heading to Mussidan +5 min
Distribution · 90 days
23 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 78% · 18
- 3–10 min 17% · 4
- 10–30 min 4% · 1
- 30+ min 0% · 0
On-time by weekday
- 80% M n=5
- 100% T n=5
- 40% W n=5
- 100% T n=4
- 75% F n=4
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 23 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 |
|---|---|---|---|
| 16:29 | on time | +4 min | |
| 16:33 / 16:34 | ≈ on time | ≈ +4 min | |
| 16:40 / 16:41 | ≈ on time | ≈ +4 min | |
| 16:45 / 16:46 | ≈ on time | ≈ +4 min | |
| 16:50 / 16:51 | ≈ on time | ≈ +4 min | |
| 16:57 / 16:58 | ≈ on time | ≈ +5 min | |
| 17:00 / 17:01 | ≈ on time | ≈ +5 min | |
| 17:05 / 17:06 | ≈ on time | ≈ +5 min | |
| 17:15 | on time | +5 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 |
|---|---|---|---|
| Wed 4 Nov | Mussidan 17:19 | +5 min | +5 min |
| Tue 3 Nov | Mussidan 17:15 | 0 min | — |
| Mon 2 Nov | Mussidan 17:14 | 0 min | — |
| Fri 30 Oct | Mussidan 17:16 | 0 min | — |
| Thu 29 Oct | Mussidan 17:16 | 0 min | — |
| Wed 28 Oct | Mussidan 17:16 | 0 min | — |
| Tue 27 Oct | Mussidan 17:16 | 0 min | — |
| Mon 26 Oct | Mussidan 17:22 | +5 min | +5 min |
| Fri 23 Oct | Mussidan 17:16 | 0 min | — |
| Thu 22 Oct | Mussidan 17:17 | 0 min | — |
| Wed 21 Oct | Mussidan 17:21 | +5 min | +5 min |
| Tue 20 Oct | Mussidan 17:16 | 0 min | — |
| Mon 19 Oct | Mussidan 17:17 | 0 min | — |
| Fri 16 Oct | Mussidan 17:26 | +10 min | +10 min |
| Thu 15 Oct | Mussidan 17:16 | 0 min | — |
| Wed 14 Oct | Mussidan 17:16 | 0 min | — |
| Tue 13 Oct | Mussidan 17:16 | 0 min | — |
| Mon 12 Oct | Mussidan 17:16 | 0 min | — |
| Fri 9 Oct | Mussidan 17:16 | 0 min | — |
| Thu 8 Oct | Mussidan 17:16 | 0 min | — |
| Wed 7 Oct | Mussidan 17:21 | +5 min | +5 min |
| Tue 6 Oct | Mussidan 17:16 | 0 min | — |
| Mon 5 Oct | Mussidan 17:16 | 0 min | — |