RB 6235 Noertzange, Gare – Rumelange, Gare

View line RB

Noertzange, Gare 10:13 → Rumelange, Gare 10:22 Mon, Tue, Wed, Thu, Fri 0 h 09 min · 4 stops CFL

✓ Today’s run finished

Today, last fix heading to Rumelange, Gare at 10:23 No data

  1. Noertzange, Gare10:13
  2. Kayl, Gare10:16
  3. Tétange, Gare10:18
  4. Rumelange, Gare10:22

Next service: tomorrow 10:13 from Noertzange, Gare · Fri 9 Oct

Next departure 10:13 tomorrow · Noertzange, Gare
On-time · 30 days
—
Too little data (0/9 runs with data)
RT coverage: 0 full · 0 partial · 9 no data
On-time · 90 days
—
Too little data (0/9 runs with data)
RT coverage: 0 full · 0 partial · 9 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 Rumelange, 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 (4 stops).

StopSched.
10:13
10:16 / 10:17
10:18 / 10:19
10:22

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
Thu 8 OctRumelange, Gare 10:23No data—
Wed 7 OctRumelange, Gare 10:24No data—
Tue 6 OctRumelange, Gare 10:23No data—
Mon 5 OctRumelange, Gare 10:23No data—
Fri 2 OctRumelange, Gare 10:21No data—
Thu 1 OctRumelange, Gare 10:21No data—
Wed 30 SeptRumelange, Gare 10:21No data—
Tue 29 SeptRumelange, Gare 10:21No data—
Mon 28 SeptRumelange, Gare 10:21No data—