L 13799 Wavre – Fleurus

View line L

Wavre 15:10 → Fleurus 15:55 Sat, Sun 0 h 45 min · 12 stops SNCB/NMBS

It does not run today

Last recorded run: Sunday 8 November No data

On-time · 30 days
—
Too little data (0/12 runs with data)
RT coverage: 0 full · 0 partial · 12 no data
On-time · 90 days
—
Too little data (0/12 runs with data)
RT coverage: 0 full · 0 partial · 12 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 Fleurus, 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 (12 stops).

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

StopSched.
Wavre
15:10
Bierges-Walibi
15:13 / 15:14
Limal
15:17
Ottignies
15:21 / 15:24
Céroux-Mousty
15:27
Court-Saint-Etienne
15:29 / 15:31
Faux
15:34 / 15:35
La Roche (brabant)
15:38
Villers-la-Ville
15:42 / 15:43
Tilly
15:46 / 15:47
Ligny
15:52
Fleurus
15:55

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 NovFleurus 15:54No data—
Sat 7 NovFleurus 15:54No data—
Fri 30 OctJurbise 16:49No data—
Thu 29 OctJurbise 16:49No data—
Wed 28 OctJurbise 16:49No data—
Tue 27 OctJurbise 16:49No data—
Mon 26 OctJurbise 16:50No data—
Fri 23 OctJurbise 16:50No data—
Thu 22 OctJurbise 16:50No data—
Wed 21 OctJurbise 16:49No data—
Tue 20 OctJurbise 16:49No data—
Mon 19 OctJurbise 16:49No data—