P 7984 Alost – Burst

View line P

Alost 08:07 → Burst 08:24 Mon, Tue, Wed, Thu, Fri 0 h 17 min · 6 stops SNCB/NMBS

✓ Today’s run finished

Today, last fix heading to Burst at 08:25 No data

  1. Alost08:07
  2. Alost Kerrebroek08:10
  3. Vijfhuizen08:14
  4. Erpe-Mere08:17
  5. Bambrugge08:21
  6. Burst08:24

Next service: tomorrow 08:07 from Alost · Fri 23 Oct

Next departure 08:07 tomorrow · Alost
On-time · 30 days
—
Too little data (0/14 runs with data)
RT coverage: 0 full · 0 partial · 14 no data
On-time · 90 days
—
Too little data (0/14 runs with data)
RT coverage: 0 full · 0 partial · 14 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.
08:07
08:10
08:14
08:17
08:21
08:24

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