C76 839262 Reims – Laon

View line C76

Reims 14:41 → Laon 15:19 Mon, Tue, Wed, Thu, Fri 0 h 38 min · 5 stops SNCF

It does not run today

Last recorded run: Friday 13 November 0 min

Next service: Monday 14:41 from Reims · Mon 16 Nov

Next departure 14:41 Monday · Reims
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 18 full · 1 partial · 1 no data
On-time · 90 days
94%
31/33 runs under 3 min
RT coverage: 32 full · 1 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 Laon, in minutes. One bar per run.

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

Worst days

  • Tue 27 Oct Max en route +20 min · last fix heading to Laon +20 min
  • Thu 12 Nov Max en route +10 min · last fix heading to Laon +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 31
  • 3–10 min 0% · 0
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 86% T n=7
  • 100% W n=6
  • 83% T n=6
  • 100% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 33 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
14:41on time on time
14:50≈ on time ≈ on time
14:57 / 14:58≈ on time ≈ on time
15:06 / 15:07≈ on time ≈ on time
15: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
Fri 13 NovLaon 15:190 min—
Thu 12 NovLaon 15:29+10 min+10 min
Tue 10 NovLaon 15:190 min—
Mon 9 NovLaon 15:190 min—
Fri 6 NovLaon 15:190 min—
Thu 5 NovLaon 15:19No data—
Wed 4 NovLaon 15:190 min—
Tue 3 NovLaon 15:190 min—
Mon 2 NovLaon 15:190 min—
Fri 30 OctLaon 15:200 min—
Thu 29 OctLaon 15:200 min—
Wed 28 OctLaon 15:200 min—
Tue 27 OctLaon 15:40+20 min+20 min
Mon 26 OctLaon 15:210 min—
Fri 23 OctLoivre 14:44Partial coverage0 min—
Thu 22 OctLaon 15:200 min—
Wed 21 OctLaon 15:200 min—
Tue 20 OctLaon 15:200 min—
Mon 19 OctLaon 15:210 min—
Fri 16 OctLaon 15:200 min—
Thu 15 OctLaon 15:200 min—
Wed 14 OctLaon 15:210 min—
Tue 13 OctLaon 15:200 min—
Mon 12 OctLaon 15:200 min—
Fri 9 OctLaon 15:200 min—
Thu 8 OctLaon 15:200 min—
Wed 7 OctLaon 15:200 min—
Tue 6 OctLaon 15:200 min—
Mon 5 OctLaon 15:200 min—
Fri 21 AugStopPoint:OCETrain TER-8729601 15:180 min—