P 8980 Alost – Burst

View line P

Alost 16:31 → Burst 16:47 Mon, Tue, Wed, Thu, Fri 0 h 16 min · 6 stops SNCB/NMBS

It does not run today

Last recorded run: Friday 23 October No data

Next service: Monday 16:31 from Alost · Mon 26 Oct

Full trip card
Next departure 16:31 Monday · Alost
On-time · 30 days
—
Too little data (0/15 runs with data)
RT coverage: 0 full · 0 partial · 15 no data
On-time · 90 days
—
Too little data (0/15 runs with data)
RT coverage: 0 full · 0 partial · 15 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 Burst, 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 (6 stops).

StopSched.
Alost
16:31
Alost Kerrebroek
16:34
Vijfhuizen
16:38
Erpe-Mere
16:41
Bambrugge
16:44
Burst
16:47

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
Fri 23 OctBurst 16:49No data—
Thu 22 OctBurst 16:49No data—
Wed 21 OctBurst 16:48No data—
Tue 20 OctBurst 16:48No data—
Mon 19 OctBurst 16:48No data—
Fri 16 OctBurst 16:48No data—
Thu 15 OctBurst 16:48No data—
Wed 14 OctBurst 16:48No data—
Tue 13 OctBurst 16:49No data—
Mon 12 OctBurst 16:48No data—
Fri 9 OctBurst 16:48No data—
Thu 8 OctBurst 16:48No data—
Wed 7 OctBurst 16:48No data—
Tue 6 OctBurst 16:48No data—
Mon 5 OctBurst 16:48No data—