C70 839655 Champagne-Ardenne TGV – Reims

View line C70

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

It does not run today

Last recorded run: Friday 13 November 0 min

Next service: tomorrow 09:10 from Champagne-Ardenne TGV · Mon 16 Nov

Next departure 09:10 tomorrow · Champagne-Ardenne TGV
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 18 full · 0 partial · 0 no data
On-time · 90 days
100%
28/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
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

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 100% · 28
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (4 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
09:10on time on time
09:15 / 09:16≈ on time ≈ on time
09:17 / 09:18≈ on time ≈ on time
09:22on 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 NovReims 09:230 min—
Thu 12 NovReims 09:240 min—
Tue 10 NovReims 09:230 min—
Mon 9 NovReims 09:230 min—
Fri 6 NovReims 09:230 min—
Thu 5 NovReims 09:230 min—
Wed 4 NovReims 09:230 min—
Mon 2 NovReims 09:230 min—
Fri 30 OctReims 09:230 min—
Thu 29 OctReims 09:230 min—
Wed 28 OctReims 09:230 min—
Tue 27 OctReims 09:230 min—
Mon 26 OctReims 09:230 min—
Fri 23 OctReims 09:230 min—
Thu 22 OctReims 09:230 min—
Wed 21 OctReims 09:230 min—
Tue 20 OctReims 09:230 min—
Mon 19 OctReims 09:230 min—
Fri 16 OctReims 09:230 min—
Thu 15 OctReims 09:230 min—
Wed 14 OctReims 09:230 min—
Tue 13 OctReims 09:230 min—
Mon 12 OctReims 09:240 min—
Fri 9 OctReims 09:240 min—
Thu 8 OctReims 09:230 min—
Wed 7 OctReims 09:240 min—
Tue 6 OctReims 09:230 min—
Mon 5 OctStopPoint:OCETrain TE~3dd22c0f 09:240 min—