P24 885601 Grenoble – Gap
Alerts for train 885601
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line P24.
✓ Today’s run finished
Today it reached Gap at 10:58 +15 min
- Grenoble08:09
- Jarrie - Vizille08:22
- Saint-Georges-de-Commiers08:28
- Monestier-de-Clermont08:54
- Lus-la-Croix-Haute09:45
- Aspres-sur-Buëch10:13
- Gap10:43
Next service: tomorrow 08:09 from Grenoble · Mon 9 Nov
Last 30 days
Arrival delay at Gap, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sun 8 Nov Max en route +15 min · last fix heading to Gap +15 min
- Thu 1 Oct Max en route +5 min · last fix heading to StopPoint:OCETrain TER-8776300 +5 min
Distribution · 90 days
8 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 75% · 6
- 3–10 min 13% · 1
- 10–30 min 13% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=1
- 100% W n=1
- 0% T n=1
- 100% F n=1
- 100% S n=1
- 50% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 8 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 |
|---|---|---|---|
| 08:09 | on time | on time | |
| 08:15 / 08:16 | ≈ on time | ≈ on time | |
| 08:22 / 08:23 | ≈ on time | ≈ +1 min | |
| 08:28 / 08:29 | ≈ on time | ≈ +1 min | |
| 08:31 / 08:32 | ≈ on time | ≈ +1 min | |
| 08:54 / 08:57 | ≈ on time | ≈ +2 min | |
| 09:12 / 09:13 | ≈ on time | ≈ +3 min | |
| 09:45 / 09:46 | ≈ on time | ≈ +5 min | |
| 10:13 / 10:14 | ≈ on time | ≈ +6 min | |
| 10:22 / 10:23 | ≈ on time | ≈ +7 min | |
| 10:43 | on time | +8 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 |
|---|---|---|---|
| Sun 8 Nov | Gap 10:59 | +15 min | +15 min |
| Sat 7 Nov | Gap 10:44 | 0 min | — |
| Sun 4 Oct | StopPoint:OCETrain TE~ccbf101a 10:44 | 0 min | — |
| Fri 2 Oct | StopPoint:OCETrain TER-8776300 10:42 | 0 min | — |
| Thu 1 Oct | StopPoint:OCETrain TER-8776300 10:43 | +5 min | +5 min |
| Wed 30 Sept | StopPoint:OCETrain TER-8776300 10:43 | 0 min | — |
| Tue 29 Sept | StopPoint:OCETrain TER-8776300 10:42 | 0 min | — |
| Mon 28 Sept | StopPoint:OCETrain TER-8776300 10:42 | 0 min | +5 min |