K59 86565 Rodange – Luxembourg

View line K59

Rodange 14:00 → Luxembourg 14:27 Mon, Tue, Wed, Thu, Fri 0 h 27 min · 6 stops SNCF

It has not run yet today

Last recorded run: Friday 30 October 0 min

Next service: today 14:00 from Rodange · Mon 9 Nov

Next departure 14:00 today · Rodange
On-time · 30 days
80%
8/10 runs under 3 min
RT coverage: 10 full · 0 partial · 5 no data
On-time · 90 days
83%
24/29 runs under 3 min
RT coverage: 29 full · 0 partial · 16 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

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

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

Worst days

  • Wed 14 Oct Max en route +10 min · last fix heading to Luxembourg +10 min
  • Thu 15 Oct Max en route +5 min · last fix heading to Luxembourg +5 min
  • Tue 6 Oct Max en route +5 min · last fix heading to Luxembourg +5 min
  • Wed 16 Sept Max en route +5 min · last fix heading to StopPoint:OCETrain TER-8200710 +5 min
  • Tue 8 Sept Max en route +5 min · last fix heading to StopPoint:OCETrain TER-8200710 +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 24
  • 3–10 min 14% · 4
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 60% T n=5
  • 67% W n=6
  • 83% T n=6
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 29 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
14:00on time on time
14:03 / 14:04≈ on time ≈ +1 min
14:07 / 14:09≈ on time ≈ +1 min
14:13 / 14:15≈ on time ≈ +2 min
14:22 / 14:24≈ on time ≈ +4 min
14:27on time +5 min

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
Fri 30 OctLuxembourg 14:280 min—
Thu 29 OctLuxembourg 14:280 min—
Wed 28 OctLuxembourg 14:280 min—
Tue 27 OctLuxembourg 14:280 min—
Mon 26 OctLuxembourg 14:290 min—
Fri 23 OctLuxembourg 14:28No data—
Thu 22 OctLuxembourg 14:28No data—
Wed 21 OctLuxembourg 14:28No data—
Tue 20 OctLuxembourg 14:28No data—
Mon 19 OctLuxembourg 14:28No data—
Fri 16 OctLuxembourg 14:280 min—
Thu 15 OctLuxembourg 14:33+5 min+5 min
Wed 14 OctLuxembourg 14:38+10 min+10 min
Tue 13 OctLuxembourg 14:280 min—
Mon 12 OctLuxembourg 14:280 min—
Fri 9 OctLuxembourg 14:280 min—
Thu 8 OctLuxembourg 14:280 min—
Wed 7 OctLuxembourg 14:280 min—
Tue 6 OctLuxembourg 14:33+5 min+5 min
Mon 5 OctLuxembourg 14:280 min—
Mon 28 SeptStopPoint:OCETrain TER-8200100 14:270 min—
Mon 21 SeptStopPoint:OCETrain TER-8200100 14:260 min—
Fri 18 SeptStopPoint:OCETrain TER-8200100 14:270 min—
Thu 17 SeptStopPoint:OCETrain TER-8200100 14:260 min+5 min
Wed 16 SeptStopPoint:OCETrain TER-8200710 14:27+5 min+5 min
Tue 15 SeptStopPoint:OCETrain TER-8200100 14:260 min—
Mon 14 SeptStopPoint:OCETrain TER-8200100 14:260 min—
Fri 11 SeptStopPoint:OCETrain TER-8200100 14:260 min—
Thu 10 SeptStopPoint:OCETrain TER-8200100 14:260 min—
Wed 9 SeptStopPoint:OCETrain TER-8200100 14:260 min—