C4 855265 Vitré – Rennes

View line C4

Vitré 17:23 → Rennes 17:53 Mon, Tue, Wed, Thu, Fri 0 h 30 min · 6 stops SNCF

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 17:23 from Vitré · Fri 6 Nov

Next departure 17:23 today · Vitré
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 17 full · 0 partial · 3 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 20 full · 0 partial · 3 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: 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 23 Oct Max en route +20 min · last fix heading to Rennes +20 min
  • Wed 7 Oct Max en route +5 min · last fix heading to Rennes +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 18
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 75% W n=4
  • 100% T n=3
  • 67% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 20 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
17:23on time on time
17:32 / 17:33≈ on time ≈ on time
17:37 / 17:38≈ on time ≈ on time
17:41 / 17:42≈ on time ≈ on time
17:46 / 17:47≈ on time ≈ on time
17:53on time +1 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
Thu 5 NovRennes 17:54No data—
Wed 4 NovRennes 17:540 min—
Tue 3 NovRennes 17:550 min—
Mon 2 NovRennes 17:540 min—
Fri 30 OctRennes 17:54No data—
Wed 28 OctRennes 17:54No data—
Tue 27 OctRennes 17:540 min—
Mon 26 OctRennes 17:550 min—
Fri 23 OctRennes 18:15+20 min+20 min
Thu 22 OctRennes 17:550 min—
Wed 21 OctRennes 17:550 min—
Tue 20 OctRennes 17:540 min—
Mon 19 OctRennes 17:540 min—
Fri 16 OctRennes 17:540 min—
Thu 15 OctRennes 17:540 min—
Wed 14 OctRennes 17:540 min—
Tue 13 OctRennes 17:540 min—
Mon 12 OctRennes 17:540 min—
Fri 9 OctRennes 17:540 min—
Thu 8 OctRennes 17:550 min—
Wed 7 OctRennes 17:59+5 min+5 min
Tue 6 OctRennes 17:540 min—
Mon 5 OctRennes 17:540 min—