P 7987 Burst – Alost
View line P
Alerts for train 7987
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line P.
It does not run today
Last recorded run: Wednesday 21 October No data
Next service: Wednesday 13:12 from Burst · Wed 28 Oct
Next departure 13:12 Wednesday · Burst
On-time · 30 days
—
Too little data (0/3 runs with data)
RT coverage: 0 full · 0 partial · 3 no data
On-time · 90 days
—
Too little data (0/3 runs with data)
RT coverage: 0 full · 0 partial · 3 no data
Typical delay
—
Needs at least 5 runs with data (0 so far)
P90
—
Needs at least 5 runs with data (0 so far)
Last 30 days
Arrival delay at Alost, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Distribution · 90 days
No runs with a known final delay yet.
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
| Stop | Sched. |
|---|---|
| 13:12 | |
| 13:15 | |
| 13:19 | |
| 13:22 | |
| 13:26 | |
| 13:28 |
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 3 October 2026.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 21 Oct | Alost 13:30 | No data | — |
| Wed 14 Oct | Alost 13:30 | No data | — |
| Wed 7 Oct | Alost 13:29 | No data | — |