803B 2819 Paris-Est – Luxembourg

View line 803B

Paris-Est 15:24 → Luxembourg 17:36 Sun 2 h 12 min · 3 stops SNCF

✓ Today’s run finished

Today, last fix heading to Metz Ville at 16:42 +2 min

  1. Paris-Est15:24
  2. Metz Ville16:47
  3. Luxembourg17:36

Next service: Sunday 15:24 from Paris-Est · Sun 15 Nov

Next departure 15:24 Sunday · Paris-Est
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 21 full · 1 partial · 8 no data
On-time · 90 days
93%
27/29 runs under 3 min
RT coverage: 28 full · 1 partial · 8 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
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

  • Sun 25 Oct Max en route +5 min · last fix heading to Olten +5 min
  • Sun 18 Oct Max en route +3 min · last fix heading to Olten +3 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=1
  • 100% T n=5
  • 100% W n=5
  • 100% T n=1
  • 100% F n=5
  • 100% S n=5
  • 71% S n=7

Stops and timetable

Timetable of the latest run from the operator’s GTFS (3 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
15:24on time on time
16:47 / 16:53≈ on time ≈ +2 min
17:36+1 min +2 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
Sun 8 NovMetz Ville 16:42Partial coverage+2 min+2 min
Sat 7 NovOlten 11:540 min—
Fri 6 NovOlten 11:540 min—
Thu 5 NovOlten 11:54No data—
Wed 4 NovOlten 11:540 min—
Tue 3 NovOlten 11:54+1 min—
Mon 2 NovOlten 11:54No data—
Sun 1 NovOlten 11:55+1 min—
Sat 31 OctOlten 11:55+1 min—
Fri 30 OctOlten 11:550 min—
Thu 29 OctOlten 11:55No data—
Wed 28 OctOlten 11:56+1 min+1 min
Tue 27 OctOlten 11:56+1 min—
Mon 26 OctOlten 11:56No data—
Sun 25 OctOlten 11:59+5 min+5 min
Sat 24 OctOlten 11:56+1 min—
Fri 23 OctOlten 11:550 min—
Thu 22 OctOlten 11:55No data—
Wed 21 OctOlten 11:56+1 min—
Tue 20 OctOlten 11:56+1 min+1 min
Mon 19 OctOlten 11:55No data—
Sun 18 OctOlten 11:59+3 min+3 min
Sat 17 OctOlten 11:56+1 min—
Fri 16 OctOlten 11:550 min—
Thu 15 OctOlten 11:55No data—
Wed 14 OctOlten 11:550 min—
Tue 13 OctOlten 11:550 min—
Mon 12 OctOlten 11:55No data—
Sun 11 OctOlten 11:57+2 min+2 min
Sat 10 OctOlten 11:57+2 min+2 min