C4 855205 Vitré – Rennes

View line C4

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

✓ Today’s run finished

Today it reached Rennes at 06:58 +10 min

  1. Vitré06:14
  2. Les Lacs06:20
  3. Châteaubourg06:26
  4. Servon06:31
  5. Noyal - Acigné06:36
  6. Cesson-Sévigné06:41
  7. Rennes06:48

Next service: tomorrow 06:14 from Vitré · Tue 10 Nov

Next departure 06:14 tomorrow · Vitré
On-time · 30 days
79%
15/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
86%
24/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
+5min
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 9 Nov Max en route +10 min · last fix heading to Rennes +10 min
  • Mon 26 Oct Max en route +5 min · last fix heading to Rennes +5 min
  • Thu 15 Oct Max en route +5 min · last fix heading to Rennes +5 min
  • Wed 14 Oct Max en route +5 min · last fix heading to Rennes +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 86% · 24
  • 3–10 min 11% · 3
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 78% M n=9
  • 100% T n=5
  • 80% W n=5
  • 75% T n=4
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (7 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
06:14on time on time
06:20 / 06:21≈ on time ≈ +1 min
06:26 / 06:27≈ on time ≈ +2 min
06:31 / 06:32≈ on time ≈ +3 min
06:36 / 06:37≈ on time ≈ +3 min
06:41 / 06:42≈ on time ≈ +4 min
06:48on 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
Mon 9 NovRennes 06:59+10 min+10 min
Fri 6 NovRennes 06:490 min—
Thu 5 NovRennes 06:49No data—
Wed 4 NovRennes 06:490 min—
Tue 3 NovRennes 06:490 min—
Mon 2 NovRennes 06:490 min—
Fri 30 OctRennes 06:490 min—
Thu 29 OctRennes 06:490 min—
Wed 28 OctRennes 06:490 min—
Tue 27 OctRennes 06:490 min—
Mon 26 OctRennes 06:54+5 min+5 min
Fri 23 OctRennes 06:490 min—
Thu 22 OctRennes 06:490 min—
Wed 21 OctRennes 06:490 min—
Tue 20 OctRennes 06:490 min—
Mon 19 OctRennes 06:490 min—
Fri 16 OctRennes 06:490 min—
Thu 15 OctRennes 06:54+5 min+5 min
Wed 14 OctRennes 06:54+5 min+5 min
Tue 13 OctRennes 06:490 min—
Fri 9 OctRennes 06:490 min—
Thu 8 OctRennes 06:490 min—
Wed 7 OctRennes 06:490 min—
Tue 6 OctRennes 06:500 min—
Mon 5 OctStopPoint:OCETrain TE~29da617a 06:500 min—
Mon 28 SeptStopPoint:OCETrain TER-8747100 06:470 min—
Mon 14 SeptStopPoint:OCETrain TER-8747100 06:470 min—
Mon 7 SeptStopPoint:OCETrain TER-8747100 06:470 min—
Mon 31 AugStopPoint:OCETrain TER-8747100 06:470 min—