P4 17365 Romans - Bourg-de-Péage – Gap
Alerts for train 17365
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line P4.
✓ Today’s run finished
Today it reached Gap at 20:30 +1 min
- Romans - Bourg-de-Péage17:38
- Valence17:56
- Livron18:10
- Saillans18:46
- Die19:09
- Veynes-Devoluy20:06
- Gap20:29
Next service: tomorrow 17:38 from Romans - Bourg-de-Péage · Tue 17 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
- Wed 7 Oct Max en route +22 min · last fix heading to Olten +22 min
- Tue 27 Oct Max en route +5 min · last fix heading to Olten +5 min
- Thu 12 Nov Max en route +4 min · last fix heading to Gap +4 min
Distribution · 90 days
74 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 1% · 1
- On time 95% · 70
- 3–10 min 3% · 2
- 10–30 min 1% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=10
- 89% T n=9
- 91% W n=11
- 90% T n=10
- 100% F n=11
- 100% S n=13
- 100% S n=10
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 74 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:38 | on time | on time | |
| 17:45 / 17:47 | ≈ on time | ≈ on time | |
| 17:56 / 17:59 | ≈ on time | ≈ on time | |
| 18:10 / 18:12 | ≈ on time | ≈ on time | |
| 18:29 / 18:33 | ≈ on time | ≈ on time | |
| 18:46 / 18:48 | ≈ on time | ≈ +1 min | |
| 19:09 / 19:11 | ≈ on time | ≈ +1 min | |
| 19:28 / 19:29 | ≈ on time | ≈ +1 min | |
| 20:06 / 20:09 | ≈ on time | ≈ +1 min | |
| 20:29 | on time | +2 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 | Gap 20:29 | +1 min | +1 min |
| Sun 15 Nov | Briançon 22:13 | 0 min | — |
| Sat 14 Nov | Gap 20:29 | 0 min | — |
| Fri 13 Nov | Briançon 22:13 | 0 min | — |
| Thu 12 Nov | Gap 20:30 | +4 min | +4 min |
| Wed 11 Nov | Briançon 22:13 | 0 min | — |
| Tue 10 Nov | Gap 20:29 | 0 min | — |
| Mon 9 Nov | Gap 20:29 | +2 min | +2 min |
| Sun 8 Nov | Briançon 22:13 | 0 min | — |
| Sat 7 Nov | Gap 20:29 | 0 min | — |
| Fri 6 Nov | Briançon 22:14 | +2 min | +2 min |
| Thu 5 Nov | Gap 20:29 | 0 min | — |
| Wed 4 Nov | Gap 20:29 | +1 min | +1 min |
| Tue 3 Nov | Gap 20:29 | 0 min | — |
| Mon 2 Nov | Gap 20:29 | 0 min | — |
| Sun 1 Nov | Briançon 22:13 | 0 min | — |
| Sat 31 Oct | Olten 18:40 | −1 min | — |
| Fri 30 Oct | Olten 18:41 | 0 min | — |
| Thu 29 Oct | Olten 18:42 | +1 min | +1 min |
| Wed 28 Oct | Olten 18:42 | 0 min | — |
| Tue 27 Oct | Olten 18:46 | +5 min | +5 min |
| Mon 26 Oct | Olten 18:41 | 0 min | — |
| Sun 25 Oct | Olten 18:41 | 0 min | — |
| Sat 24 Oct | Olten 18:42 | +1 min | — |
| Fri 23 Oct | Olten 18:41 | 0 min | — |
| Thu 22 Oct | Olten 18:43 | +2 min | +2 min |
| Wed 21 Oct | Olten 18:41 | +1 min | — |
| Tue 20 Oct | Olten 18:41 | 0 min | — |
| Mon 19 Oct | Olten 18:41 | 0 min | — |
| Sun 18 Oct | Tecknau 18:33 | 0 min | — |