C76 839257 Laon – Reims

View line C76

Laon 08:11 → Reims 08:49 Mon, Tue, Wed, Thu, Fri 0 h 38 min · 5 stops SNCF

✓ Today’s run finished

Today it reached Reims at 08:49 0 min

  1. Laon08:11
  2. Saint-Erme08:23
  3. Guignicourt08:32
  4. Loivre08:39
  5. Reims08:49

Next service: tomorrow 08:11 from Laon · Fri 20 Nov

Next departure 08:11 tomorrow · Laon
On-time · 30 days
79%
15/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
84%
26/31 runs under 3 min
RT coverage: 31 full · 0 partial · 1 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: +7 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

Worst days

  • Fri 23 Oct Max en route +100 min · last fix heading to Reims +100 min
  • Thu 29 Oct Max en route +15 min · last fix heading to Reims +15 min
  • Fri 6 Nov Max en route +5 min · last fix heading to Reims +5 min
  • Mon 26 Oct Max en route +5 min · last fix heading to Reims +5 min
  • Tue 20 Oct Max en route +5 min · last fix heading to Reims +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 26
  • 3–10 min 10% · 3
  • 10–30 min 3% · 1
  • 30+ min 3% · 1

On-time by weekday

  • 83% M n=6
  • 86% T n=7
  • 100% W n=6
  • 83% T n=6
  • 67% 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, 31 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
08:11on time +5 min
08:23 / 08:24≈ on time ≈ +5 min
08:32 / 08:33≈ on time ≈ +5 min
08:39 / 08:40≈ on time ≈ +5 min
08:49on 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
Thu 19 NovReims 08:490 min—
Wed 18 NovReims 08:490 min—
Tue 17 NovReims 08:490 min—
Mon 16 NovReims 08:490 min—
Fri 13 NovReims 08:490 min—
Thu 12 NovReims 08:490 min—
Tue 10 NovReims 08:490 min—
Mon 9 NovReims 08:490 min—
Fri 6 NovReims 08:54+5 min+5 min
Thu 5 NovReims 08:49No data—
Wed 4 NovReims 08:490 min—
Tue 3 NovReims 08:490 min—
Fri 30 OctReims 08:500 min—
Thu 29 OctReims 09:05+15 min+15 min
Wed 28 OctReims 08:500 min—
Tue 27 OctReims 08:500 min—
Mon 26 OctReims 08:55+5 min+5 min
Fri 23 OctReims 10:30+100 min+100 min
Thu 22 OctReims 08:500 min—
Wed 21 OctReims 08:500 min—
Tue 20 OctReims 08:55+5 min+5 min
Mon 19 OctReims 08:500 min—
Fri 16 OctReims 08:500 min—
Thu 15 OctReims 08:500 min—
Wed 14 OctReims 08:500 min—
Tue 13 OctReims 08:500 min—
Mon 12 OctReims 08:510 min—
Fri 9 OctReims 08:510 min—
Thu 8 OctReims 08:500 min—
Wed 7 OctReims 08:510 min—