C76 839269 Laon – Reims

View line C76

Laon 16:39 → Reims 17:19 Mon, Tue, Wed, Thu, Fri 0 h 40 min · 5 stops SNCF

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 16:39 from Laon · Tue 17 Nov

Next departure 16:39 today · Laon
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 18 full · 0 partial · 1 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 30 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: 0 min

Last 30 days

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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 30
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=6
  • 100% W n=5
  • 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 (5 stops).

Last 90 days, 30 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
16:39on time on time
16:51 / 16:52≈ on time ≈ on time
17:00 / 17:01≈ on time ≈ on time
17:09 / 17:10≈ on time ≈ on time
17:19on 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 16 NovReims 17:190 min—
Fri 13 NovReims 17:190 min—
Thu 12 NovReims 17:190 min—
Tue 10 NovReims 17:190 min—
Mon 9 NovReims 17:190 min—
Fri 6 NovReims 17:190 min—
Thu 5 NovReims 17:19No data—
Wed 4 NovReims 17:190 min—
Tue 3 NovReims 17:200 min—
Mon 2 NovReims 17:190 min—
Fri 30 OctReims 17:200 min—
Thu 29 OctReims 17:200 min—
Wed 28 OctReims 17:200 min—
Tue 27 OctReims 17:200 min—
Mon 26 OctReims 17:210 min—
Thu 22 OctReims 17:210 min—
Wed 21 OctReims 17:200 min—
Tue 20 OctReims 17:200 min—
Mon 19 OctReims 17:210 min—
Fri 16 OctReims 17:200 min—
Thu 15 OctReims 17:200 min—
Wed 14 OctReims 17:200 min—
Tue 13 OctReims 17:200 min—
Mon 12 OctReims 17:200 min—
Fri 9 OctReims 17:200 min—
Thu 8 OctReims 17:200 min+5 min
Wed 7 OctReims 17:200 min—
Tue 6 OctReims 17:200 min—
Mon 5 OctReims 17:210 min—
Fri 21 AugStopPoint:OCETrain TER-8717100 17:180 min—