C4 855249 Vitré – Rennes

View line C4

Vitré 16:06 → Rennes 16:38 Mon, Tue, Wed, Thu, Fri 0 h 32 min · 7 stops SNCF

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 16:06 from Vitré · Mon 9 Nov

Next departure 16:06 today · 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
83%
20/24 runs under 3 min
RT coverage: 24 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

  • Fri 23 Oct Max en route +25 min · last fix heading to Rennes +25 min
  • Tue 3 Nov Max en route +5 min · last fix heading to Rennes +5 min
  • Thu 22 Oct Max en route +5 min · last fix heading to Rennes +5 min
  • Tue 13 Oct Max en route +5 min · last fix heading to Rennes +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 20
  • 3–10 min 13% · 3
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 60% T n=5
  • 100% W n=5
  • 75% T n=4
  • 80% 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, 24 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
16:06on time on time
16:12 / 16:13≈ on time ≈ +1 min
16:17 / 16:18≈ on time ≈ +2 min
16:22 / 16:23≈ on time ≈ +3 min
16:27 / 16:28≈ on time ≈ +3 min
16:32 / 16:33≈ on time ≈ +4 min
16:38on 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
Fri 6 NovRennes 16:390 min—
Thu 5 NovRennes 16:39No data—
Wed 4 NovRennes 16:390 min—
Tue 3 NovRennes 16:45+5 min+5 min
Mon 2 NovRennes 16:390 min—
Fri 30 OctRennes 16:390 min—
Thu 29 OctRennes 16:390 min—
Wed 28 OctRennes 16:390 min—
Tue 27 OctRennes 16:390 min—
Mon 26 OctRennes 16:400 min—
Fri 23 OctRennes 17:05+25 min+25 min
Thu 22 OctRennes 16:44+5 min+5 min
Wed 21 OctRennes 16:390 min—
Tue 20 OctRennes 16:390 min—
Mon 19 OctRennes 16:400 min—
Fri 16 OctRennes 16:390 min—
Thu 15 OctRennes 16:390 min—
Wed 14 OctRennes 16:390 min—
Tue 13 OctRennes 16:44+5 min+5 min
Mon 12 OctRennes 16:390 min—
Fri 9 OctRennes 16:390 min—
Thu 8 OctRennes 16:390 min—
Wed 7 OctRennes 16:390 min—
Tue 6 OctRennes 16:390 min—
Mon 5 OctRennes 16:400 min—