C4 855274 Rennes – Vitré

View line C4

Rennes 18:39 → Vitré 19:12 Mon, Tue, Wed, Thu, Fri 0 h 33 min · 6 stops SNCF

It does not run today

Last recorded run: Thursday 5 November No data

Next service: Monday 18:39 from Rennes · Mon 9 Nov

Next departure 18:39 Monday · Rennes
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 18 full · 0 partial · 1 no data
On-time · 90 days
88%
37/42 runs under 3 min
RT coverage: 42 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +7 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

  • Fri 23 Oct Max en route +80 min · last fix heading to Vitré +80 min
  • Tue 8 Sept Max en route +15 min · last fix heading to StopPoint:OCETrain TER-8747152 +15 min
  • Wed 21 Oct Max en route +10 min · last fix heading to Vitré +10 min
  • Wed 28 Oct Max en route +5 min · last fix heading to Vitré +5 min
  • Thu 24 Sept Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8747150 +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 37
  • 3–10 min 5% · 2
  • 10–30 min 5% · 2
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=10
  • 90% T n=10
  • 80% W n=10
  • 89% T n=9
  • 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, 42 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
18:39on time on time
18:44 / 18:45≈ on time ≈ +1 min
18:49 / 18:50≈ on time ≈ +1 min
18:54 / 18:55≈ on time ≈ +2 min
18:59 / 19:00≈ on time ≈ +3 min
19:12on 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
Thu 5 NovVitré 19:13No data—
Wed 4 NovVitré 19:130 min—
Tue 3 NovVitré 19:140 min—
Mon 2 NovVitré 19:130 min—
Thu 29 OctVitré 19:130 min—
Wed 28 OctVitré 19:18+5 min+5 min
Tue 27 OctVitré 19:130 min—
Mon 26 OctVitré 19:140 min—
Fri 23 OctVitré 20:34+80 min+80 min
Thu 22 OctVitré 19:130 min—
Wed 21 OctVitré 19:23+10 min+10 min
Tue 20 OctVitré 19:130 min—
Mon 19 OctVitré 19:130 min—
Fri 16 OctVitré 19:130 min—
Thu 15 OctVitré 19:130 min—
Wed 14 OctVitré 19:130 min—
Tue 13 OctVitré 19:140 min—
Mon 12 OctVitré 19:130 min—
Fri 9 OctVitré 19:130 min—
Thu 8 OctVitré 19:130 min—
Wed 7 OctVitré 19:130 min—
Tue 6 OctVitré 19:130 min—
Mon 5 OctVitré 19:130 min—
Thu 1 OctStopPoint:OCETrain TER-8747150 19:110 min—
Wed 30 SeptStopPoint:OCETrain TER-8747150 19:110 min—
Tue 29 SeptStopPoint:OCETrain TER-8747150 19:110 min—
Mon 28 SeptStopPoint:OCETrain TER-8747150 19:110 min—
Thu 24 SeptStopPoint:OCETrain TER-8747150 19:12+5 min+10 min
Wed 23 SeptStopPoint:OCETrain TER-8747150 19:110 min—
Tue 22 SeptStopPoint:OCETrain TER-8747150 19:110 min—