L 13796 Wavre – Fleurus

View line L

Wavre 12:10 → Fleurus 12: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/13 runs with data)
RT coverage: 0 full · 0 partial · 13 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.
12:10
12:13 / 12:14
12:17
12:21 / 12:24
12:27
12:29 / 12:31
12:34 / 12:35
12:38
12:42 / 12:43
12:46 / 12:47
12:52
12: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 12:54No data—
Sat 7 NovFleurus 12:54No data—
Fri 30 OctJurbise 13:49No data—
Thu 29 OctJurbise 13:49No data—
Wed 28 OctJurbise 13:49No data—
Tue 27 OctJurbise 13:49No data—
Mon 26 OctJurbise 13:49No data—
Fri 23 OctJurbise 13:50No data—
Thu 22 OctJurbise 13:49No data—
Wed 21 OctJurbise 13:50No data—
Tue 20 OctJurbise 13:50No data—
Mon 19 OctJurbise 13:49No data—
Sun 4 OctQuévy 16:26No data—