C6 885470 Grenoble Universités - Gières → Rives

View line C6

Grenoble Universités - Gières 16:10 → Rives 16:55 Mon, Tue, Wed, Thu, Fri 0 h 45 min · 8 stops SNCF

TER 885470 Grenoble Universités - Gières–Rives: final delay under 3 min on 15 of its 18 runs with data in the last 30 days (83%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 05:25 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 16:10 from Grenoble Universités - Gières · Mon 23 Nov

Next departure 16:10 tomorrow · Grenoble Universités - Gières
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 18 full · 0 partial · 0 no data
On-time · 90 days
84%
48/57 runs under 3 min
RT coverage: 57 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Mon 19 Oct Max en route +30 min · last fix heading to Rives +30 min
  • Mon 26 Oct Max en route +15 min · last fix heading to Rives +15 min
  • Tue 1 Sept Max en route +15 min · last fix heading to StopPoint:OCETrain TER-8774728 +15 min
  • Mon 7 Sept Max en route +20 min · last fix heading to StopPoint:OCETrain TER-8774728 +10 min
  • Tue 25 Aug Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8774728 +10 min

Distribution · 90 days

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

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

On-time by weekday

  • 73% M n=11
  • 69% T n=13
  • 100% W n=12
  • 90% T n=10
  • 91% F n=11
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 57 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:14 / 16:15≈ on time ≈ +1 min
16:21 / 16:24≈ on time ≈ +2 min
16:33 / 16:34≈ on time ≈ +3 min
16:37 / 16:38≈ on time ≈ +3 min
16:44 / 16:45≈ on time ≈ +4 min
16:50 / 16:51≈ on time ≈ +4 min
16:55on time +5 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 20 NovRives 16:540 min—
Thu 19 NovRives 16:540 min—
Wed 18 NovMoirans 16:340 min—
Tue 17 NovRives 16:540 min—
Mon 16 NovRives 16:540 min—
Fri 13 NovRives 17:00+5 min+5 min
Thu 12 NovRives 16:540 min—
Tue 10 NovRives 17:02+5 min+5 min
Mon 9 NovRives 16:540 min—
Fri 6 NovRives 16:540 min—
Wed 4 NovRives 16:540 min—
Tue 3 NovRives 16:550 min—
Mon 2 NovRives 16:540 min—
Fri 30 OctRives 16:560 min—
Thu 29 OctRives 16:560 min—
Wed 28 OctRives 16:560 min—
Tue 27 OctRives 16:560 min—
Mon 26 OctRives 17:12+15 min+15 min
Fri 23 OctRives 16:570 min—
Thu 22 OctRives 16:570 min—
Wed 21 OctRives 16:560 min—
Tue 20 OctRives 16:560 min—
Mon 19 OctRives 17:27+30 min+30 min
Fri 16 OctRives 16:560 min—
Thu 15 OctRives 17:01+5 min+10 min
Wed 14 OctRives 16:560 min—
Tue 13 OctRives 16:560 min+5 min
Mon 12 OctRives 16:560 min—
Fri 9 OctRives 16:560 min—
Thu 8 OctRives 16:560 min—