P11 863033 Tours – Poitiers
Alerts for train 863033
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line P11.
✓ Today’s run finished
Today it reached Poitiers at 08:48 +5 min
- Tours07:31
- Villeperdue07:45
- Maillé07:58
- Les Ormes08:07
- Dangé-Saint-Romain08:11
- Châtellerault08:23
- Poitiers08:43
Next service: Monday 07:31 from Tours · Mon 9 Nov
Last 30 days
Arrival delay at Poitiers, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Mon 26 Oct Max en route +10 min · last fix heading to Poitiers +10 min
- Fri 6 Nov Max en route +5 min · last fix heading to Poitiers +5 min
- Fri 30 Oct Max en route +5 min · last fix heading to Poitiers +5 min
- Wed 21 Oct Max en route +5 min · last fix heading to Poitiers +5 min
Distribution · 90 days
25 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 84% · 21
- 3–10 min 12% · 3
- 10–30 min 4% · 1
- 30+ min 0% · 0
On-time by weekday
- 80% M n=5
- 100% T n=5
- 80% W n=5
- 100% T n=5
- 60% F n=5
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 25 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 |
|---|---|---|---|
| 07:31 | on time | on time | |
| 07:39 / 07:40 | ≈ on time | ≈ +1 min | |
| 07:45 / 07:46 | ≈ on time | ≈ +1 min | |
| 07:53 / 07:54 | ≈ on time | ≈ +2 min | |
| 07:58 / 07:59 | ≈ on time | ≈ +2 min | |
| 08:03 / 08:04 | ≈ on time | ≈ +2 min | |
| 08:07 / 08:08 | ≈ on time | ≈ +3 min | |
| 08:11 / 08:12 | ≈ on time | ≈ +3 min | |
| 08:17 / 08:18 | ≈ on time | ≈ +3 min | |
| 08:23 / 08:24 | ≈ on time | ≈ +4 min | |
| 08:35 / 08:36 | ≈ on time | ≈ +4 min | |
| 08:43 | 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 |
|---|---|---|---|
| Fri 6 Nov | Poitiers 08:49 | +5 min | +5 min |
| Thu 5 Nov | Poitiers 08:44 | 0 min | — |
| Wed 4 Nov | Poitiers 08:44 | 0 min | — |
| Tue 3 Nov | Poitiers 08:44 | 0 min | — |
| Mon 2 Nov | Poitiers 08:44 | 0 min | — |
| Fri 30 Oct | Poitiers 08:49 | +5 min | +5 min |
| Thu 29 Oct | Poitiers 08:44 | 0 min | — |
| Wed 28 Oct | Poitiers 08:44 | 0 min | — |
| Tue 27 Oct | Poitiers 08:44 | 0 min | — |
| Mon 26 Oct | Poitiers 08:54 | +10 min | +10 min |
| Fri 23 Oct | Poitiers 08:44 | 0 min | — |
| Thu 22 Oct | Poitiers 08:44 | 0 min | — |
| Wed 21 Oct | Poitiers 08:49 | +5 min | +5 min |
| Tue 20 Oct | Poitiers 08:44 | 0 min | — |
| Mon 19 Oct | Poitiers 08:44 | 0 min | — |
| Fri 16 Oct | Poitiers 08:44 | 0 min | +5 min |
| Thu 15 Oct | Poitiers 08:44 | 0 min | — |
| Wed 14 Oct | Poitiers 08:44 | 0 min | — |
| Tue 13 Oct | Poitiers 08:44 | 0 min | — |
| Mon 12 Oct | Poitiers 08:45 | 0 min | — |
| Fri 9 Oct | Poitiers 08:44 | 0 min | — |
| Thu 8 Oct | Poitiers 08:44 | 0 min | — |
| Wed 7 Oct | Poitiers 08:45 | 0 min | — |
| Tue 6 Oct | Poitiers 08:44 | 0 min | — |
| Mon 5 Oct | StopPoint:OCETrain TE~43650e0b 08:45 | 0 min | — |