S10 2060 Jette – Alost

View line S10

Jette 09:43 → Alost 10:57 Sat, Sun 1 h 14 min · 19 stops SNCB/NMBS

✓ Today’s run finished

Today, last fix heading to Alost at 10:58 No data

  1. Jette09:43
  2. Bruxelles-Ouest09:52
  3. Bruxelles-Nord10:11
  4. Berchem-Sainte-Agathe10:23
  5. Sint-Martens-Bodegem10:33
  6. Liedekerke10:43
  7. Alost10:57
On-time · 30 days
—
Too little data (0/5 runs with data)
RT coverage: 0 full · 0 partial · 5 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 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).

StopSched.
09:43
09:47
09:50
09:52 / 09:53
09:58 / 10:02
10:06 / 10:07
10:11 / 10:13
10:16 / 10:17
10:19 / 10:20
10:23 / 10:24
10:26
10:29 / 10:30
10:33
10:36 / 10:37
10:41
10:43 / 10:44
10:47 / 10:49
10:52 / 10:53
10: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 25 OctAlost 10:58No data—
Sat 24 OctAlost 10:58No data—
Sun 18 OctAlost 10:58No data—
Sat 17 OctAlost 10:58No data—
Sun 4 OctAlost 10:58No data—