RE 1818 Kautenbach, Gare – Wiltz, Gare

View line RE

Kautenbach, Gare 18:33 → Wiltz, Gare 18:45 Mon, Tue, Wed, Thu, Fri 0 h 12 min · 3 stops CFL

✓ Today’s run finished

Today, last fix heading to Wiltz, Gare at 18:46 No data

  1. Kautenbach, Gare18:33
  2. Merkholtz, Gare18:38
  3. Wiltz, Gare18:45

Next service: tomorrow 18:33 from Kautenbach, Gare · Wed 7 Oct

Full trip card
Next departure 18:33 tomorrow · Kautenbach, Gare
On-time · 30 days
—
Too little data (0/7 runs with data)
RT coverage: 0 full · 0 partial · 7 no data
On-time · 90 days
—
Too little data (0/7 runs with data)
RT coverage: 0 full · 0 partial · 7 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 Wiltz, Gare, 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 (3 stops).

StopSched.
Kautenbach, Gare
18:33
Merkholtz, Gare
18:38
Wiltz, Gare
18: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 28 September 2026.

Recent runs

DateLast stopFinalMax
Tue 6 OctWiltz, Gare 18:46No data—
Mon 5 OctWiltz, Gare 18:46No data—
Fri 2 OctWiltz, Gare 18:44No data—
Thu 1 OctWiltz, Gare 18:44No data—
Wed 30 SeptWiltz, Gare 18:44No data—
Tue 29 SeptWiltz, Gare 18:44No data—
Mon 28 SeptWiltz, Gare 18:44No data—