C70 839669 Champagne-Ardenne TGV – Reims

View line C70

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

✓ Today’s run finished

Today it reached Reims at 19:52 0 min

  1. Champagne-Ardenne TGV19:40
  2. Reims Maison Blanche19:45
  3. Franchet d'Esperey19:47
  4. Reims19:52

Next service: tomorrow 19:40 from Champagne-Ardenne TGV · Fri 20 Nov

Next departure 19:40 tomorrow · Champagne-Ardenne TGV
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 1 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 29 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 29
  • 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=6
  • 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, 29 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
19:40on time on time
19:45 / 19:46≈ on time ≈ on time
19:47 / 19:48≈ on time ≈ on time
19:52on 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
Thu 19 NovReims 19:530 min—
Wed 18 NovReims 19:530 min—
Tue 17 NovReims 19:530 min—
Mon 16 NovReims 19:530 min—
Fri 13 NovReims 19:540 min—
Thu 12 NovReims 19:530 min—
Tue 10 NovReims 19:530 min—
Mon 9 NovReims 19:530 min—
Fri 6 NovReims 19:530 min—
Thu 5 NovReims 19:54No data—
Wed 4 NovReims 19:530 min—
Fri 30 OctReims 19:530 min—
Thu 29 OctReims 19:530 min—
Tue 27 OctReims 19:530 min—
Mon 26 OctReims 19:540 min—
Fri 23 OctReims 19:540 min—
Thu 22 OctReims 19:530 min—
Wed 21 OctReims 19:530 min—
Tue 20 OctReims 19:530 min—
Mon 19 OctReims 19:530 min—
Fri 16 OctReims 19:530 min—
Thu 15 OctReims 19:530 min—
Wed 14 OctReims 19:530 min—
Tue 13 OctReims 19:530 min—
Mon 12 OctReims 19:530 min—
Fri 9 OctReims 19:530 min—
Thu 8 OctReims 19:530 min—
Wed 7 OctReims 19:530 min—
Tue 6 OctReims 19:530 min—
Mon 5 OctReims 19:530 min—