C4 855227 Vitré – Rennes

View line C4

Vitré 09:05 → Rennes 09:37 Mon, Tue, Wed, Thu, Fri 0 h 32 min · 6 stops SNCF

✓ Today’s run finished

Today it reached Rennes at 09:37 0 min

  1. Vitré09:05
  2. Châteaubourg09:15
  3. Servon09:20
  4. Noyal - Acigné09:25
  5. Cesson-Sévigné09:30
  6. Rennes09:37

Next service: Monday 09:05 from Vitré · Mon 9 Nov

Next departure 09:05 Monday · Vitré
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 10 full · 0 partial · 1 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 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

Worst days

  • Fri 28 Aug Max en route +50 min · last fix heading to StopPoint:OCETrain TER-8747150 +50 min
  • Mon 5 Oct Max en route +5 min · last fix heading to StopPoint:OCETrain TE~29da617a +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 4% · 1

On-time by weekday

  • 80% M n=5
  • 100% T n=6
  • 100% W n=6
  • 100% T n=5
  • 83% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 28 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
09:05on time on time
09:15 / 09:16≈ on time ≈ on time
09:20 / 09:21≈ on time ≈ on time
09:25 / 09:26≈ on time ≈ on time
09:30 / 09:31≈ on time ≈ on time
09:37on 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
Fri 6 NovRennes 09:380 min—
Thu 5 NovRennes 09:38No data—
Wed 4 NovRennes 09:380 min—
Tue 3 NovRennes 09:380 min—
Fri 30 OctRennes 09:380 min—
Thu 29 OctRennes 09:380 min—
Wed 28 OctRennes 09:380 min—
Tue 27 OctRennes 09:380 min—
Mon 26 OctRennes 09:380 min—
Fri 9 OctRennes 09:390 min—
Thu 8 OctRennes 09:380 min—
Wed 7 OctRennes 09:390 min—
Tue 6 OctRennes 09:380 min—
Mon 5 OctStopPoint:OCETrain TE~29da617a 09:44+5 min+5 min
Fri 28 AugStopPoint:OCETrain TER-8747150 09:36+50 min+50 min
Thu 27 AugStopPoint:OCETrain TER-8747100 09:360 min—
Wed 26 AugStopPoint:OCETrain TER-8747100 09:360 min—
Tue 25 AugStopPoint:OCETrain TER-8747100 09:370 min—
Mon 24 AugStopPoint:OCETrain TER-8747100 09:360 min—
Fri 21 AugStopPoint:OCETrain TER-8747100 09:360 min—
Thu 20 AugStopPoint:OCETrain TER-8747100 09:360 min—
Wed 19 AugStopPoint:OCETrain TER-8747100 09:360 min—
Tue 18 AugStopPoint:OCETrain TER-8747100 09:360 min—
Mon 17 AugStopPoint:OCETrain TER-8747100 09:360 min—
Fri 14 AugStopPoint:OCETrain TER-8747100 09:360 min—
Thu 13 AugStopPoint:OCETrain TER-8747100 09:360 min—
Wed 12 AugStopPoint:OCETrain TER-8747100 09:360 min—
Tue 11 AugStopPoint:OCETrain TER-8747100 09:360 min—
Mon 10 AugStopPoint:OCETrain TER-8747100 09:360 min—