C6 885472 Grenoble – Rives

View line C6

Grenoble 17:09 → Rives 17:40 Mon, Tue, Wed, Thu, Fri 0 h 31 min · 6 stops SNCF

It does not run today

Last recorded run: Friday 13 November +25 min

Next service: Monday 17:09 from Grenoble · Mon 16 Nov

Next departure 17:09 Monday · Grenoble
On-time · 30 days
79%
15/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
90%
35/39 runs under 3 min
RT coverage: 39 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +17 min

Last 30 days

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

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

Worst days

  • Fri 13 Nov Max en route +25 min · last fix heading to Rives +25 min
  • Mon 9 Nov Max en route +25 min · last fix heading to Rives +25 min
  • Fri 30 Oct Max en route +20 min · last fix heading to Rives +15 min
  • Fri 23 Oct Max en route +5 min · last fix heading to Rives +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 35
  • 3–10 min 3% · 1
  • 10–30 min 8% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 100% T n=7
  • 100% W n=11
  • 100% T n=6
  • 57% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 39 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
17:09on time on time
17:18 / 17:19≈ on time ≈ +1 min
17:23 / 17:24≈ on time ≈ +1 min
17:29 / 17:30≈ on time ≈ +1 min
17:35 / 17:36≈ on time ≈ +1 min
17:40on time +1 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 13 NovRives 18:05+25 min+25 min
Thu 12 NovRives 17:390 min—
Tue 10 NovRives 17:390 min—
Mon 9 NovRives 18:04+25 min+25 min
Fri 6 NovRives 17:390 min—
Wed 4 NovRives 17:390 min—
Tue 3 NovRives 17:420 min—
Mon 2 NovRives 17:390 min—
Fri 30 OctRives 17:56+15 min+20 min
Thu 29 OctRives 17:410 min—
Wed 28 OctRives 17:410 min—
Tue 27 OctRives 17:410 min—
Mon 26 OctRives 17:420 min—
Fri 23 OctRives 17:47+5 min+5 min
Thu 22 OctRives 17:420 min—
Wed 21 OctRives 17:420 min—
Tue 20 OctRives 17:410 min—
Mon 19 OctRives 17:420 min—
Fri 16 OctRives 17:410 min—
Thu 15 OctRives 17:410 min—
Wed 14 OctRives 17:410 min—
Tue 13 OctRives 17:410 min—
Mon 12 OctRives 17:410 min—
Fri 9 OctRives 17:410 min—
Thu 8 OctRives 17:420 min—
Wed 7 OctRives 17:410 min—
Tue 6 OctRives 17:410 min—
Mon 5 OctRives 17:410 min—
Wed 30 SeptStopPoint:OCETrain TER-8774724 17:390 min—
Wed 23 SeptStopPoint:OCETrain TER-8774724 17:390 min—