C50 88812 Thionville – Luxembourg

View line C50

Thionville 17:36 → Luxembourg 18:06 Mon, Tue, Wed, Thu, Fri 0 h 30 min · 4 stops SNCF

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 17:36 from Thionville · Wed 11 Nov

Next departure 17:36 today · Thionville
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
On-time · 90 days
93%
42/45 runs under 3 min
RT coverage: 45 full · 0 partial · 1 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: +2 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 30 Sept Max en route +30 min · last fix heading to StopPoint:OCETrain TER-8200603 +20 min
  • Fri 6 Nov Max en route +20 min · last fix heading to Luxembourg +16 min
  • Fri 11 Sept Max en route +25 min · last fix heading to StopPoint:OCETrain TER-8200100 +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 42
  • 3–10 min 2% · 1
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 100% T n=9
  • 89% W n=9
  • 100% T n=8
  • 78% F n=9
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 45 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
17:36on time on time
17:42 / 17:43≈ on time ≈ +1 min
17:51 / 17:53≈ on time ≈ +2 min
18:06on 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 NovLuxembourg 18:070 min—
Mon 9 NovLuxembourg 18:070 min—
Fri 6 NovLuxembourg 18:24+16 min+20 min
Wed 4 NovLuxembourg 18:070 min—
Tue 3 NovLuxembourg 18:080 min—
Mon 2 NovLuxembourg 18:070 min—
Fri 16 OctLuxembourg 18:070 min—
Thu 15 OctLuxembourg 18:070 min—
Wed 14 OctLuxembourg 18:070 min—
Tue 13 OctLuxembourg 18:070 min—
Mon 12 OctLuxembourg 18:070 min—
Fri 9 OctLuxembourg 18:070 min—
Thu 8 OctLuxembourg 18:080 min—
Wed 7 OctLuxembourg 18:070 min—
Tue 6 OctHettange-Grande 17:40Partial coverageNo data—
Mon 5 OctLuxembourg 18:070 min—
Fri 2 OctStopPoint:OCETrain TER-8200100 18:050 min+10 min
Thu 1 OctStopPoint:OCETrain TER-8200100 18:060 min+5 min
Wed 30 SeptStopPoint:OCETrain TER-8200603 18:05+20 min+30 min
Tue 29 SeptStopPoint:OCETrain TER-8200100 18:050 min+5 min
Mon 28 SeptStopPoint:OCETrain TER-8200100 18:050 min+5 min
Fri 25 SeptStopPoint:OCETrain TER-8200100 18:050 min+30 min
Thu 24 SeptStopPoint:OCETrain TER-8200100 18:060 min—
Wed 23 SeptStopPoint:OCETrain TER-8200100 18:050 min—
Tue 22 SeptStopPoint:OCETrain TER-8200100 18:050 min—
Mon 21 SeptStopPoint:OCETrain TER-8200100 18:050 min+5 min
Fri 18 SeptStopPoint:OCETrain TER-8200100 18:050 min+30 min
Thu 17 SeptStopPoint:OCETrain TER-8200100 18:050 min—
Wed 16 SeptStopPoint:OCETrain TER-8200100 18:050 min—
Tue 15 SeptStopPoint:OCETrain TER-8200100 18:050 min—