C70 839657 Champagne-Ardenne TGV → Reims

View line C70

Champagne-Ardenne TGV 09:40 → Reims 09:52 Mon, Tue, Wed, Thu, Fri 0 h 12 min · 4 stops SNCF

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: Monday 09:40 from Champagne-Ardenne TGV · Mon 23 Nov

Next departure 09:40 Monday · Champagne-Ardenne TGV
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
82%
27/33 runs under 3 min
RT coverage: 33 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: +1 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

  • Tue 3 Nov Max en route +10 min · last fix heading to Reims +10 min
  • Thu 22 Oct Max en route +10 min · last fix heading to Reims +10 min
  • Fri 23 Oct Max en route +5 min · last fix heading to Reims +5 min
  • Wed 21 Oct Max en route +5 min · last fix heading to Reims +5 min
  • Wed 14 Oct Max en route +5 min · last fix heading to Reims +5 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 82% · 27
  • 3–10 min 12% · 4
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (4 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
09:40on time +5 min
09:45 / 09:46≈ on time ≈ +5 min
09:47 / 09:48≈ on time ≈ +5 min
09:52on 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
Fri 20 NovReims 09:540 min—
Thu 19 NovReims 09:530 min+5 min
Wed 18 NovReims 09:530 min—
Tue 17 NovReims 09:530 min—
Mon 16 NovReims 09:530 min—
Fri 13 NovReims 09:530 min—
Thu 12 NovReims 09:540 min—
Tue 10 NovReims 09:540 min—
Mon 9 NovReims 09:530 min—
Fri 6 NovReims 09:530 min—
Thu 5 NovReims 09:53No data—
Wed 4 NovReims 09:530 min+5 min
Tue 3 NovReims 10:04+10 min+10 min
Mon 2 NovReims 09:530 min—
Fri 30 OctReims 09:530 min—
Thu 29 OctReims 09:530 min—
Wed 28 OctReims 09:530 min—
Tue 27 OctReims 09:530 min+5 min
Mon 26 OctReims 09:530 min—
Fri 23 OctReims 09:58+5 min+5 min
Thu 22 OctReims 10:03+10 min+10 min
Wed 21 OctReims 09:58+5 min+5 min
Tue 20 OctReims 09:530 min—
Mon 19 OctReims 09:530 min—
Fri 16 OctReims 09:530 min—
Thu 15 OctReims 09:530 min—
Wed 14 OctReims 09:58+5 min+5 min
Tue 13 OctReims 09:530 min—
Mon 12 OctReims 09:540 min—
Fri 9 OctReims 09:540 min—