S10 3869 Termonde – Alost

View line S10

Termonde 19:09 → Alost 20: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 19:09 from Termonde · Sat 14 Nov

Next departure 19: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.
19:09
19:12
19:14 / 19:15
19:18
19:21 / 19:22
19:25 / 19:26
19:29
19:32 / 19:33
19:38
19:42 / 19:43
19:47
19:50
19:52 / 19:53
19:58 / 20:02
20:05 / 20:06
20:10 / 20:12
20:16 / 20:17
20:19 / 20:20
20:23 / 20:24
20:26
20:29 / 20:30
20:33
20:36 / 20:37
20:41
20:43 / 20:44
20:47 / 20:49
20:52 / 20:53
20: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 20:58No data—
Sat 7 NovAlost 20:58No data—
Sun 1 NovAlost 20:58No data—
Sat 31 OctAlost 20:59No data—
Sun 18 OctAlost 20:58No data—
Sat 17 OctAlost 20:58No data—
Sun 11 OctAlost 20:58No data—
Sun 4 OctAlost 20:59No data—