S10 2057 Bruxelles-Midi – Alost
Alerts for train 2057
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 1 November No data
Next service: tomorrow 07:02 from Bruxelles-Midi · Sat 7 Nov
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 (15 stops).
Not enough runs yet to work out the usual delay by stop.
| Stop | Sched. |
|---|---|
| 07:02 | |
| 07:05 / 07:06 | |
| 07:10 / 07:12 | |
| 07:16 / 07:17 | |
| 07:19 / 07:20 | |
| 07:23 / 07:24 | |
| 07:26 | |
| 07:29 / 07:30 | |
| 07:33 | |
| 07:36 / 07:37 | |
| 07:41 | |
| 07:43 / 07:44 | |
| 07:47 / 07:49 | |
| 07:52 / 07:53 | |
| 07: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 1 Nov | Alost 07:59 | No data | — |
| Sat 31 Oct | Alost 07:58 | No data | — |
| Sun 25 Oct | Alost 07:58 | No data | — |
| Sat 24 Oct | Alost 07:58 | No data | — |
| Sun 18 Oct | Alost 07:58 | No data | — |
| Sat 17 Oct | Alost 07:58 | No data | — |
| Sun 11 Oct | Alost 07:58 | No data | — |
| Sat 10 Oct | Alost 07:58 | No data | — |
| Sun 4 Oct | Alost 07:58 | No data | — |