K59 86548 Luxembourg – Longwy

View line K59

Luxembourg 05:04 → Longwy 05:39 Mon, Tue, Wed, Thu, Fri 0 h 35 min · 7 stops SNCF

✓ Today’s run finished

Today it reached Longwy at 05:39 0 min

  1. Luxembourg05:04
  2. Luxembourg secteur Hollerich05:06
  3. Dippach secteur Reckange05:14
  4. Bascharage secteur Sanem05:20
  5. Petange05:24
  6. Rodange05:31
  7. Longwy05:39

Next service: tomorrow 05:04 from Luxembourg · Tue 10 Nov

Full trip card
Next departure 05:04 tomorrow · Luxembourg
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 16 full · 0 partial · 0 no data
On-time · 90 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 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 Longwy, 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 28 Oct Max en route +5 min · last fix heading to Longwy +5 min
  • Tue 6 Oct Max en route +5 min · last fix heading to Longwy +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 93% · 27
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 80% T n=5
  • 83% W n=6
  • 100% T n=6
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (7 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
Luxembourg
05:04on time on time
Luxembourg secteur Hollerich
05:06 / 05:07≈ on time ≈ on time
Dippach secteur Reckange
05:14 / 05:16≈ on time ≈ on time
Bascharage secteur Sanem
05:20 / 05:21≈ on time ≈ on time
Petange
05:24 / 05:27≈ on time ≈ on time
Rodange
05:31 / 05:32≈ on time ≈ on time
Longwy
05:39on 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
Mon 9 NovLongwy 05:390 min—
Fri 30 OctLongwy 05:400 min—
Thu 29 OctLongwy 05:400 min—
Wed 28 OctLongwy 05:45+5 min+5 min
Tue 27 OctLongwy 05:410 min—
Mon 26 OctLongwy 05:400 min—
Fri 23 OctLongwy 05:400 min—
Thu 22 OctLongwy 05:400 min—
Wed 21 OctLongwy 05:400 min—
Tue 20 OctLongwy 05:400 min—
Mon 19 OctLongwy 05:400 min—
Fri 16 OctLongwy 05:400 min—
Thu 15 OctLongwy 05:400 min—
Wed 14 OctLongwy 05:400 min—
Tue 13 OctLongwy 05:400 min—
Mon 12 OctLongwy 05:400 min—
Fri 9 OctLongwy 05:400 min—
Thu 8 OctLongwy 05:400 min—
Wed 7 OctLongwy 05:400 min—
Tue 6 OctLongwy 05:45+5 min+5 min
Mon 5 OctStopPoint:OCETrain TE~17ffdc33 05:410 min—
Fri 21 AugStopPoint:OCETrain TER-8719400 05:380 min—
Thu 20 AugStopPoint:OCETrain TER-8719400 05:380 min—
Wed 19 AugStopPoint:OCETrain TER-8719400 05:380 min—
Tue 18 AugStopPoint:OCETrain TER-8719400 05:380 min—
Mon 17 AugStopPoint:OCETrain TER-8719400 05:380 min—
Fri 14 AugStopPoint:OCETrain TER-8719400 05:380 min—
Thu 13 AugStopPoint:OCETrain TER-8719400 05:380 min—
Wed 12 AugStopPoint:OCETrain TER-8719400 05:380 min—