C71 839628 Châlons-en-Champagne – Reims

View line C71

Châlons-en-Champagne 17:12 → Reims 17:55 Mon, Tue, Thu, Fri 0 h 43 min · 6 stops SNCF

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 17:12 from Châlons-en-Champagne · Mon 9 Nov

Next departure 17:12 today · Châlons-en-Champagne
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 24 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

Worst days

  • Fri 23 Oct Max en route +10 min · last fix heading to Reims +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 80% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 24 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
17:12on time on time
17:27 / 17:28≈ on time ≈ on time
17:33 / 17:34≈ on time ≈ on time
17:37 / 17:38≈ on time ≈ on time
17:42 / 17:43≈ on time ≈ on time
17:55on 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 6 NovReims 17:540 min—
Thu 5 NovReims 17:54No data—
Wed 4 NovReims 17:540 min—
Tue 3 NovReims 17:550 min—
Mon 2 NovReims 17:540 min—
Fri 30 OctReims 17:560 min—
Thu 29 OctReims 17:560 min—
Wed 28 OctReims 17:560 min—
Tue 27 OctReims 17:560 min—
Mon 26 OctReims 17:570 min—
Fri 23 OctReims 18:07+10 min+10 min
Thu 22 OctReims 17:570 min—
Wed 21 OctReims 17:570 min—
Tue 20 OctReims 17:560 min—
Mon 19 OctReims 17:560 min—
Fri 16 OctReims 17:560 min—
Thu 15 OctReims 17:560 min—
Wed 14 OctReims 17:560 min—
Tue 13 OctReims 17:560 min—
Mon 12 OctReims 17:560 min—
Fri 9 OctReims 17:560 min—
Thu 8 OctReims 17:560 min—
Wed 7 OctReims 17:560 min—
Tue 6 OctReims 17:560 min—
Mon 5 OctReims 17:560 min—