C4 855207 Vitré – Rennes

View line C4

Vitré 06:40 → Rennes 07:14 Mon, Tue, Wed, Thu, Fri 0 h 34 min · 7 stops SNCF

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: Monday 06:40 from Vitré · Mon 9 Nov

Next departure 06:40 Monday · Vitré
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 18 full · 0 partial · 2 no data
On-time · 90 days
89%
34/38 runs under 3 min
RT coverage: 38 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +5 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

Worst days

  • Mon 2 Nov Max en route +10 min · last fix heading to Rennes +10 min
  • Thu 10 Sept Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8733449 +10 min
  • Tue 3 Nov Max en route +5 min · last fix heading to Rennes +5 min
  • Mon 26 Oct Max en route +5 min · last fix heading to Rennes +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 34
  • 3–10 min 5% · 2
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 78% M n=9
  • 89% T n=9
  • 100% W n=8
  • 88% T n=8
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 38 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
06:40on time on time
06:46 / 06:47≈ on time ≈ on time
06:52 / 06:53≈ on time ≈ +1 min
06:56 / 06:57≈ on time ≈ +1 min
07:01 / 07:02≈ on time ≈ +1 min
07:07 / 07:08≈ on time ≈ +1 min
07:14on time +2 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 6 NovRennes 07:140 min—
Thu 5 NovRennes 07:140 min—
Wed 4 NovRennes 07:140 min—
Tue 3 NovRennes 07:19+5 min+5 min
Mon 2 NovRennes 07:24+10 min+10 min
Fri 30 OctRennes 07:15No data—
Thu 29 OctRennes 07:15No data—
Tue 27 OctRennes 07:150 min—
Mon 26 OctRennes 07:20+5 min+5 min
Fri 23 OctRennes 07:150 min—
Thu 22 OctRennes 07:150 min—
Wed 21 OctRennes 07:150 min—
Tue 20 OctRennes 07:150 min—
Mon 19 OctRennes 07:150 min—
Fri 16 OctRennes 07:150 min—
Thu 15 OctRennes 07:160 min—
Wed 14 OctRennes 07:150 min—
Tue 13 OctRennes 07:150 min—
Mon 12 OctRennes 07:150 min—
Fri 9 OctRennes 07:160 min—
Thu 8 OctRennes 07:150 min—
Wed 7 OctRennes 07:150 min—
Tue 6 OctRennes 07:160 min—
Mon 5 OctStopPoint:OCETrain TE~29da617a 07:160 min—
Thu 24 SeptStopPoint:OCETrain TER-8747100 07:140 min—
Wed 23 SeptStopPoint:OCETrain TER-8747100 07:130 min—
Tue 22 SeptStopPoint:OCETrain TER-8747100 07:130 min—
Mon 21 SeptStopPoint:OCETrain TER-8747100 07:130 min—
Thu 17 SeptStopPoint:OCETrain TER-8747100 07:130 min—
Wed 16 SeptStopPoint:OCETrain TER-8747100 07:140 min—