S10 3870 Termonde – Bruxelles-Midi
View line S10
Alerts for train 3870
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.
On-time · 30 days
—
Too little data (0/4 runs with data)
RT coverage: 0 full · 0 partial · 4 no data
On-time · 90 days
—
Too little data (0/5 runs with data)
RT coverage: 0 full · 0 partial · 5 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 Bruxelles-Midi, 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 (14 stops).
Not enough runs yet to work out the usual delay by stop.
| Stop | Sched. |
|---|---|
| 20:09 | |
| 20:12 | |
| 20:14 / 20:15 | |
| 20:18 | |
| 20:21 / 20:22 | |
| 20:25 / 20:26 | |
| 20:29 | |
| 20:32 / 20:33 | |
| 20:38 | |
| 20:42 / 20:43 | |
| 20:47 | |
| 20:50 | |
| 20:52 / 20:53 | |
| 20:58 |
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 11 Nov | Bruxelles-Midi 20:59 | No data | — |
| Sun 25 Oct | Alost 21:58 | No data | — |
| Sun 18 Oct | Alost 21:58 | No data | — |
| Sat 17 Oct | Alost 21:58 | No data | — |
| Sun 4 Oct | Alost 21:59 | No data | — |