K59 86564 Luxembourg – Rodange

View line K59

Luxembourg 12:34 → Rodange 13:01 Mon, Tue, Wed, Thu, Fri 0 h 27 min · 6 stops SNCF

It has not run yet today

Last recorded run: Tuesday 10 November No data

Next service: today 12:34 from Luxembourg · Wed 11 Nov

Next departure 12:34 today · Luxembourg
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 9 full · 0 partial · 7 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 17 full · 0 partial · 15 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Rodange, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 5 Oct Max en route +15 min · last fix heading to Longwy +15 min

Distribution · 90 days

17 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 0% · 0
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=3
  • 100% W n=4
  • 100% T n=4
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 stops).

Last 90 days, 17 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.

StopSched.Usually 9 days in 10
12:34on time on time
12:36 / 12:37≈ on time ≈ on time
12:44 / 12:46≈ on time ≈ on time
12:50 / 12:51≈ on time ≈ on time
12:54 / 12:57≈ on time ≈ on time
13:01on time on time

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 11 July 2026.

Will I make my connection?

Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.

Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.

Recent runs

DateLast stopFinalMax
Tue 10 NovRodange 13:03No data—
Mon 9 NovRodange 13:03No data—
Fri 30 OctRodange 13:020 min—
Thu 29 OctRodange 13:020 min—
Wed 28 OctRodange 13:020 min—
Tue 27 OctRodange 13:020 min—
Mon 26 OctRodange 13:020 min—
Fri 23 OctRodange 13:02No data—
Thu 22 OctRodange 13:02No data—
Wed 21 OctRodange 13:02No data—
Tue 20 OctRodange 13:03No data—
Mon 19 OctRodange 13:02No data—
Fri 16 OctLongwy 13:100 min—
Thu 15 OctLongwy 13:100 min—
Wed 14 OctLongwy 13:100 min—
Tue 13 OctLongwy 13:100 min—
Mon 12 OctLongwy 13:100 min—
Fri 9 OctLongwy 13:100 min—
Thu 8 OctLongwy 13:100 min—
Wed 7 OctLongwy 13:100 min—
Tue 6 OctLongwy 13:100 min—
Mon 5 OctLongwy 13:25+15 min+15 min
Thu 3 SeptStopPoint:OCETrain TER-8200940 13:00No data—
Wed 2 SeptStopPoint:OCETrain TER-8200940 13:01No data—
Tue 1 SeptStopPoint:OCETrain TER-8200940 13:00No data—
Mon 31 AugStopPoint:OCETrain TER-8200940 13:00No data—
Fri 21 AugStopPoint:OCETrain TER-8200940 13:00No data—
Thu 20 AugStopPoint:OCETrain TER-8200940 13:000 min—
Wed 19 AugStopPoint:OCETrain TER-8200940 13:000 min—
Tue 18 AugStopPoint:OCETrain TER-8200940 13:00No data—