P 7667 Bertrix – Arlon

View line P

Bertrix 06:31 → Arlon 07:45 Mon, Tue, Wed, Thu, Fri 1 h 14 min · 8 stops SNCB/NMBS

It does not run today

Last recorded run: Friday 23 October No data

Next service: tomorrow 06:31 from Bertrix · Mon 26 Oct

Full trip card
Next departure 06:31 tomorrow · Bertrix
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 Arlon, 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 (8 stops).

StopSched.
Bertrix
06:31
Florenville
06:44 / 06:45
Virton
07:03 / 07:04
Halanzy
07:15 / 07:16
Aubange
07:20 / 07:21
Athus
07:28 / 07:30
Messancy
07:34 / 07:35
Arlon
07:45

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 OctArlon 07:46No data—
Thu 22 OctArlon 07:46No data—
Wed 21 OctArlon 07:46No data—
Tue 20 OctArlon 07:46No data—
Mon 19 OctArlon 07:46No data—
Fri 16 OctArlon 07:46No data—
Thu 15 OctArlon 07:46No data—
Wed 14 OctArlon 07:46No data—
Tue 13 OctArlon 07:46No data—
Mon 12 OctArlon 07:47No data—
Fri 9 OctArlon 07:47No data—
Thu 8 OctArlon 07:46No data—
Wed 7 OctArlon 07:47No data—
Tue 6 OctArlon 07:47No data—
Mon 5 OctArlon 07:47No data—