C76 839266 Reims – Laon

View line C76

Reims 16:41 → Laon 17:27 Mon, Tue, Wed, Thu, Fri 0 h 46 min · 9 stops SNCF

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 16:41 from Reims · Mon 16 Nov

Next departure 16:41 today · Reims
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 18 full · 0 partial · 0 no data
On-time · 90 days
89%
25/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +5 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 10 Nov Max en route +10 min · last fix heading to Laon +10 min
  • Mon 2 Nov Max en route +5 min · last fix heading to Laon +5 min
  • Tue 20 Oct Max en route +5 min · last fix heading to Laon +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 25
  • 3–10 min 7% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 67% T n=6
  • 100% W n=5
  • 100% T n=6
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 28 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:41on time on time
16:48 / 16:49≈ on time ≈ on time
16:52≈ on time ≈ on time
16:57 / 16:58≈ on time ≈ +1 min
17:01 / 17:02≈ on time ≈ +1 min
17:07≈ on time ≈ +1 min
17:12 / 17:13≈ on time ≈ +1 min
17:18 / 17:19≈ on time ≈ +1 min
17:27on time +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
Fri 13 NovLaon 17:290 min—
Thu 12 NovLaon 17:280 min—
Tue 10 NovLaon 17:38+10 min+10 min
Mon 9 NovLaon 17:280 min—
Fri 6 NovLaon 17:280 min—
Thu 5 NovLaon 17:280 min—
Wed 4 NovLaon 17:280 min—
Tue 3 NovLaon 17:290 min—
Mon 2 NovLaon 17:33+5 min+5 min
Fri 30 OctLaon 17:280 min—
Thu 29 OctLaon 17:280 min—
Wed 28 OctLaon 17:280 min—
Tue 27 OctLaon 17:280 min—
Mon 26 OctLaon 17:290 min—
Thu 22 OctLaon 17:290 min—
Wed 21 OctLaon 17:280 min—
Tue 20 OctLaon 17:33+5 min+5 min
Mon 19 OctLaon 17:290 min—
Fri 16 OctLaon 17:280 min—
Thu 15 OctLaon 17:280 min—
Wed 14 OctLaon 17:280 min—
Tue 13 OctLaon 17:280 min—
Mon 12 OctLaon 17:280 min—
Fri 9 OctLaon 17:280 min—
Thu 8 OctLaon 17:290 min—
Wed 7 OctLaon 17:280 min—
Tue 6 OctLaon 17:280 min—
Mon 5 OctLaon 17:270 min—