S10 3872 Jette – Alost
View line S10
Alerts for train 3872
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S10.
It does not run today
Last recorded run: Sunday 25 October No data
On-time · 30 days
—
Too little data (0/6 runs with data)
RT coverage: 0 full · 0 partial · 6 no data
On-time · 90 days
—
Too little data (0/6 runs with data)
RT coverage: 0 full · 0 partial · 6 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 (19 stops).
| Stop | Sched. |
|---|---|
| 22:43 | |
| 22:47 | |
| 22:50 | |
| 22:52 / 22:53 | |
| 22:58 / 23:02 | |
| 23:06 / 23:07 | |
| 23:11 / 23:13 | |
| 23:16 / 23:17 | |
| 23:19 / 23:20 | |
| 23:23 / 23:24 | |
| 23:26 | |
| 23:29 / 23:30 | |
| 23:33 | |
| 23:36 / 23:37 | |
| 23:41 | |
| 23:43 / 23:44 | |
| 23:47 / 23:49 | |
| 23:52 / 23:53 | |
| 23:57 |
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 |
|---|---|---|---|
| Sun 25 Oct | Alost 23:58 | No data | — |
| Sun 18 Oct | Alost 23:59 | No data | — |
| Sat 17 Oct | Alost 23:58 | No data | — |
| Sun 11 Oct | Alost 23:58 | No data | — |
| Sat 10 Oct | Alost 23:58 | No data | — |
| Sat 3 Oct | Alost 23:58 | No data | — |