C50 88804 Thionville – Luxembourg

View line C50

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

✓ Today’s run finished

Today it reached Luxembourg at 08:11 +5 min

  1. Thionville07:36
  2. Hettange-Grande07:42
  3. Bettembourg07:51
  4. Luxembourg08:06

Next service: tomorrow 07:36 from Thionville · Tue 10 Nov

Next departure 07:36 tomorrow · Thionville
On-time · 30 days
68%
13/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
75%
18/24 runs under 3 min
RT coverage: 24 full · 0 partial · 0 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

  • Fri 6 Nov Max en route +10 min · last fix heading to Luxembourg +10 min
  • Mon 9 Nov Max en route +10 min · last fix heading to Luxembourg +5 min
  • Mon 2 Nov Max en route +5 min · last fix heading to Luxembourg +5 min
  • Fri 30 Oct Max en route +5 min · last fix heading to Luxembourg +5 min
  • Wed 21 Oct Max en route +5 min · last fix heading to Luxembourg +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 18
  • 3–10 min 21% · 5
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 100% T n=4
  • 80% W n=5
  • 75% T n=4
  • 60% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 24 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
07:36on time on time
07:42 / 07:43≈ on time ≈ +2 min
07:51 / 07:53≈ on time ≈ +3 min
08:06on 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
Mon 9 NovLuxembourg 08:12+5 min+10 min
Fri 6 NovLuxembourg 08:17+10 min+10 min
Wed 4 NovLuxembourg 08:070 min—
Tue 3 NovLuxembourg 08:070 min—
Mon 2 NovLuxembourg 08:12+5 min+5 min
Fri 30 OctLuxembourg 08:12+5 min+5 min
Thu 29 OctLuxembourg 08:070 min—
Wed 28 OctLuxembourg 08:070 min—
Tue 27 OctLuxembourg 08:070 min—
Mon 26 OctLuxembourg 08:070 min—
Fri 23 OctLuxembourg 08:070 min—
Thu 22 OctLuxembourg 08:070 min—
Wed 21 OctLuxembourg 08:12+5 min+5 min
Tue 20 OctLuxembourg 08:070 min+5 min
Mon 19 OctLuxembourg 08:070 min—
Fri 16 OctLuxembourg 08:070 min—
Thu 15 OctLuxembourg 08:12+5 min+5 min
Wed 14 OctLuxembourg 08:070 min—
Mon 12 OctLuxembourg 08:070 min—
Fri 9 OctLuxembourg 08:070 min—
Thu 8 OctLuxembourg 08:070 min—
Wed 7 OctLuxembourg 08:080 min—
Tue 6 OctLuxembourg 08:070 min—
Mon 5 OctStopPoint:OCETrain TE~db460534 08:080 min—