S10 3872 Termonde – Alost

View line S10

Termonde 22:09 → Alost 23:57 Sat, Sun 1 h 48 min · 28 stops SNCB/NMBS

It does not run today

Last recorded run: Sunday 8 November No data

Next service: Saturday 22:09 from Termonde · Sat 14 Nov

Next departure 22:09 Saturday · Termonde
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/8 runs with data)
RT coverage: 0 full · 0 partial · 8 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 (28 stops).

Not enough runs yet to work out the usual delay by stop.

StopSched.
22:09
22:12
22:14 / 22:15
22:18
22:21 / 22:22
22:25 / 22:26
22:29
22:32 / 22:33
22:38
22:42 / 22:43
22:47
22:50
22:52 / 22:53
22:58 / 23:02
23:05 / 23:06
23:10 / 23:12
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

DateLast stopFinalMax
Sun 8 NovAlost 23:58No data—
Sat 7 NovAlost 23:58No data—
Sun 25 OctAlost 23:58No data—
Sun 18 OctAlost 23:59No data—
Sat 17 OctAlost 23:58No data—
Sun 11 OctAlost 23:58No data—
Sat 10 OctAlost 23:58No data—
Sat 3 OctAlost 23:58No data—