C6 859739 Nantes – Clisson

View line C6

Nantes 12:09 → Clisson 12:37 Sun 0 h 28 min · 8 stops SNCF

It does not run today

Last recorded run: Sunday 15 November 0 min

Next service: Sunday 12:09 from Nantes · Sun 22 Nov

Next departure 12:09 Sunday · Nantes
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 6 full · 0 partial · 0 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 14 full · 0 partial · 7 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 Clisson, 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

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

  • Early 0% · 0
  • On time 100% · 14
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • 100% W n=1
  • — T n=0
  • — F n=0
  • — S n=0
  • 100% S n=13

Stops and timetable

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

Last 90 days, 14 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
12:09on time on time
12:13≈ on time ≈ on time
12:16 / 12:17≈ on time ≈ on time
12:19≈ on time ≈ on time
12:25≈ on time ≈ on time
12:28 / 12:29≈ on time ≈ on time
12:33 / 12:34≈ on time ≈ on time
12:37on 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
Sun 15 NovClisson 12:390 min—
Wed 11 NovClisson 12:380 min—
Sun 8 NovClisson 12:380 min—
Sun 1 NovClisson 12:380 min—
Sun 25 OctClisson 12:380 min—
Sun 18 OctClisson 12:380 min—
Sun 11 OctClisson 12:380 min—
Sun 4 OctStopPoint:OCETrain TE~47361f74 12:380 min—
Wed 30 SeptStopPoint:OCETrain TER-8748144 12:37No data—
Sun 27 SeptStopPoint:OCETrain TER-8748144 12:360 min—
Wed 23 SeptStopPoint:OCETrain TER-8748144 12:36No data—
Sun 20 SeptStopPoint:OCETrain TER-8748144 12:370 min—
Wed 16 SeptStopPoint:OCETrain TER-8748144 12:37No data—
Sun 13 SeptStopPoint:OCETrain TER-8748144 12:360 min—
Wed 9 SeptStopPoint:OCETrain TER-8748144 12:36No data—
Sun 6 SeptStopPoint:OCETrain TER-8748144 12:360 min—
Wed 2 SeptStopPoint:OCETrain TER-8748144 12:37No data—
Sun 30 AugStopPoint:OCETrain TER-8748144 12:360 min—
Wed 26 AugStopPoint:OCETrain TER-8748144 12:36No data—
Sun 23 AugStopPoint:OCETrain TER-8748144 12:360 min—
Wed 19 AugStopPoint:OCETrain TER-8748144 12:36No data—