C4 855286 Rennes – Vitré

View line C4

Rennes 20:09 → Vitré 20:41 Mon, Tue, Wed, Thu 0 h 32 min · 6 stops SNCF

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 20:09 from Rennes · Thu 5 Nov

Next departure 20:09 today · Rennes
On-time · 30 days
76%
13/17 runs under 3 min
RT coverage: 16 full · 1 partial · 0 no data
On-time · 90 days
90%
35/39 runs under 3 min
RT coverage: 38 full · 1 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: +5 min

Last 30 days

Arrival delay at Vitré, 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 12 Oct Max en route +20 min · last fix heading to Vitré +20 min
  • Thu 15 Oct Max en route +5 min · last fix heading to Vitré +5 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Vitré +5 min
  • Wed 7 Oct Max en route +5 min · last fix heading to Cesson-Sévigné +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 8% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 90% M n=10
  • 100% T n=10
  • 90% W n=10
  • 78% T n=9
  • — 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, 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
20:09on time +1 min
20:14 / 20:15≈ on time ≈ +1 min
20:19 / 20:20≈ on time ≈ +1 min
20:24 / 20:25≈ on time ≈ +1 min
20:28 / 20:29≈ on time ≈ +1 min
20:41on 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 4 NovVitré 20:420 min—
Tue 3 NovVitré 20:430 min—
Mon 2 NovVitré 20:420 min—
Thu 29 OctVitré 20:420 min—
Wed 28 OctVitré 20:420 min—
Tue 27 OctVitré 20:420 min—
Mon 26 OctVitré 20:430 min—
Thu 22 OctVitré 20:420 min—
Wed 21 OctVitré 20:420 min—
Tue 20 OctVitré 20:420 min—
Mon 19 OctVitré 20:420 min—
Thu 15 OctVitré 20:47+5 min+5 min
Wed 14 OctVitré 20:420 min—
Tue 13 OctVitré 20:420 min—
Mon 12 OctVitré 21:02+20 min+20 min
Thu 8 OctVitré 20:47+5 min+5 min
Wed 7 OctCesson-Sévigné 20:16Partial coverage+5 min+5 min
Tue 6 OctVitré 20:420 min—
Mon 5 OctVitré 20:420 min—
Thu 1 OctStopPoint:OCETrain TER-8747150 20:400 min—
Wed 30 SeptStopPoint:OCETrain TER-8747150 20:400 min+5 min
Tue 29 SeptStopPoint:OCETrain TER-8747150 20:400 min—
Mon 28 SeptStopPoint:OCETrain TER-8747150 20:400 min—
Thu 24 SeptStopPoint:OCETrain TER-8747150 20:410 min—
Wed 23 SeptStopPoint:OCETrain TER-8747150 20:400 min—
Tue 22 SeptStopPoint:OCETrain TER-8747150 20:400 min—
Mon 21 SeptStopPoint:OCETrain TER-8747150 20:400 min—
Thu 17 SeptStopPoint:OCETrain TER-8747150 20:400 min—
Wed 16 SeptStopPoint:OCETrain TER-8747150 20:400 min—
Tue 15 SeptStopPoint:OCETrain TER-8747150 20:400 min—