C70+ 839751 Champagne-Ardenne TGV – Sedan

View line C70+

Champagne-Ardenne TGV 16:10 → Sedan 17:55 Daily 1 h 45 min · 15 stops SNCF

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 16:10 from Champagne-Ardenne TGV · Thu 19 Nov

Next departure 16:10 today · Champagne-Ardenne TGV
On-time · 30 days
86%
24/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
91%
48/53 runs under 3 min
RT coverage: 53 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: +7 min

Last 30 days

Arrival delay at Sedan, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 26 Oct Max en route +30 min · last fix heading to Sedan +30 min
  • Wed 4 Nov Max en route +10 min · last fix heading to Sedan +10 min
  • Wed 28 Oct Max en route +10 min · last fix heading to Sedan +10 min
  • Fri 13 Nov Max en route +5 min · last fix heading to Sedan +5 min
  • Sun 4 Oct Max en route +5 min · last fix heading to StopPoint:OCETrain TE~3734f160 +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 48
  • 3–10 min 4% · 2
  • 10–30 min 4% · 2
  • 30+ min 2% · 1

On-time by weekday

  • 86% M n=7
  • 100% T n=7
  • 71% W n=7
  • 100% T n=5
  • 86% F n=7
  • 100% S n=10
  • 90% S n=10

Stops and timetable

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

Last 90 days, 53 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
16:10on time on time
16:15 / 16:16≈ on time ≈ on time
16:17 / 16:18≈ on time ≈ on time
16:22 / 16:30≈ on time ≈ on time
16:39 / 16:40≈ on time ≈ +1 min
16:52 / 16:53≈ on time ≈ +2 min
16:58 / 16:59≈ on time ≈ +2 min
17:13≈ on time ≈ +2 min
17:25 / 17:30≈ on time ≈ +2 min
17:33≈ on time ≈ +2 min
17:37 / 17:38≈ on time ≈ +1 min
17:41 / 17:43≈ on time ≈ +1 min
17:46 / 17:47≈ on time ≈ +1 min
17:49 / 17:50≈ 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
Wed 18 NovSedan 17:540 min—
Tue 17 NovSedan 17:540 min—
Mon 16 NovSedan 17:570 min—
Sun 15 NovSedan 17:540 min—
Sat 14 NovSedan 17:540 min—
Fri 13 NovSedan 18:00+5 min+5 min
Thu 12 NovSedan 17:540 min—
Wed 11 NovSedan 17:540 min—
Tue 10 NovSedan 17:540 min—
Mon 9 NovSedan 17:540 min—
Sun 8 NovSedan 17:540 min—
Sat 7 NovSedan 17:540 min—
Fri 6 NovSedan 17:540 min—
Thu 5 NovSedan 17:54No data—
Wed 4 NovSedan 18:04+10 min+10 min
Tue 3 NovSedan 17:550 min—
Mon 2 NovSedan 17:540 min—
Sun 1 NovSedan 17:560 min—
Sat 31 OctSedan 17:570 min—
Fri 30 OctSedan 17:560 min—
Thu 29 OctSedan 17:560 min—
Wed 28 OctSedan 18:06+10 min+10 min
Tue 27 OctSedan 17:560 min—
Mon 26 OctSedan 18:27+30 min+30 min
Sun 25 OctSedan 17:560 min—
Sat 24 OctSedan 17:560 min—
Fri 23 OctSedan 17:570 min—
Thu 22 OctSedan 17:570 min—
Wed 21 OctSedan 17:570 min—
Tue 20 OctSedan 17:560 min—