C4 855253 Vitré – Rennes

View line C4

Vitré 16:42 → Rennes 17:12 Mon, Tue, Wed, Thu 0 h 30 min · 6 stops SNCF

✓ Today’s run finished

Today it reached Rennes at 17:12 0 min

  1. Vitré16:42
  2. Châteaubourg16:51
  3. Servon16:56
  4. Noyal - Acigné17:00
  5. Cesson-Sévigné17:05
  6. Rennes17:12

Next service: Monday 16:42 from Vitré · Mon 9 Nov

Next departure 16:42 Monday · Vitré
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 18 full · 0 partial · 0 no data
On-time · 90 days
100%
40/40 runs under 3 min
RT coverage: 40 full · 0 partial · 0 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 Rennes, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 40 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:42on time on time
16:51 / 16:52≈ on time ≈ on time
16:56 / 16:57≈ on time ≈ on time
17:00 / 17:01≈ on time ≈ on time
17:05 / 17:06≈ on time ≈ on time
17:12on 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 5 NovRennes 17:130 min—
Wed 4 NovRennes 17:130 min—
Tue 3 NovRennes 17:140 min—
Mon 2 NovRennes 17:130 min—
Thu 29 OctRennes 17:130 min—
Wed 28 OctRennes 17:130 min—
Tue 27 OctRennes 17:130 min—
Mon 26 OctRennes 17:140 min—
Thu 22 OctRennes 17:140 min—
Wed 21 OctRennes 17:130 min—
Tue 20 OctRennes 17:130 min—
Mon 19 OctRennes 17:140 min—
Thu 15 OctRennes 17:130 min—
Wed 14 OctRennes 17:130 min—
Tue 13 OctRennes 17:130 min—
Mon 12 OctRennes 17:130 min—
Thu 8 OctRennes 17:130 min—
Wed 7 OctRennes 17:130 min—
Tue 6 OctRennes 17:130 min—
Mon 5 OctRennes 17:140 min—
Thu 1 OctStopPoint:OCETrain TER-8747100 17:120 min—
Wed 30 SeptStopPoint:OCETrain TER-8747100 17:110 min—
Tue 29 SeptStopPoint:OCETrain TER-8747100 17:110 min—
Mon 28 SeptStopPoint:OCETrain TER-8747100 17:110 min—
Thu 24 SeptStopPoint:OCETrain TER-8747100 17:110 min+5 min
Wed 23 SeptStopPoint:OCETrain TER-8747100 17:110 min—
Tue 22 SeptStopPoint:OCETrain TER-8747100 17:110 min—
Mon 21 SeptStopPoint:OCETrain TER-8747100 17:110 min—
Thu 17 SeptStopPoint:OCETrain TER-8747100 17:110 min—
Wed 16 SeptStopPoint:OCETrain TER-8747100 17:110 min—