C4 855237 Vitré – Rennes

View line C4

Vitré 12:40 → Rennes 13:14 Mon, Tue, Wed, Thu, Fri 0 h 34 min · 7 stops SNCF

✓ Today’s run finished

Today it reached Rennes at 13:14 0 min

  1. Vitré12:40
  2. Les Lacs12:47
  3. Châteaubourg12:52
  4. Servon12:57
  5. Noyal - Acigné13:02
  6. Cesson-Sévigné13:07
  7. Rennes13:14

Next service: tomorrow 12:40 from Vitré · Fri 20 Nov

Next departure 12:40 tomorrow · Vitré
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 1 no data
On-time · 90 days
97%
59/61 runs under 3 min
RT coverage: 60 full · 1 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

  • Thu 8 Oct Max en route +45 min · last fix heading to Rennes +45 min
  • Thu 15 Oct Max en route +5 min · last fix heading to Rennes +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 59
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=13
  • 100% T n=13
  • 100% W n=12
  • 83% T n=12
  • 100% F n=11
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 61 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
12:40on time on time
12:47 / 12:48≈ on time ≈ on time
12:52 / 12:53≈ on time ≈ on time
12:57 / 12:58≈ on time ≈ on time
13:02 / 13:03≈ on time ≈ on time
13:07 / 13:08≈ on time ≈ on time
13:14on 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
Thu 19 NovRennes 13:140 min—
Wed 18 NovRennes 13:140 min—
Tue 17 NovRennes 13:140 min—
Mon 16 NovRennes 13:140 min—
Fri 13 NovRennes 13:140 min—
Thu 12 NovRennes 13:140 min—
Tue 10 NovRennes 13:140 min—
Mon 9 NovRennes 13:140 min—
Fri 6 NovRennes 13:140 min—
Thu 5 NovRennes 13:14No data—
Wed 4 NovRennes 13:140 min—
Tue 3 NovRennes 13:150 min—
Mon 2 NovRennes 13:140 min—
Fri 30 OctRennes 13:150 min—
Thu 29 OctRennes 13:150 min—
Wed 28 OctRennes 13:150 min—
Tue 27 OctRennes 13:150 min—
Mon 26 OctRennes 13:150 min—
Fri 23 OctRennes 13:160 min—
Thu 22 OctRennes 13:150 min—
Wed 21 OctRennes 13:150 min—
Tue 20 OctRennes 13:160 min—
Mon 19 OctRennes 13:150 min—
Fri 16 OctRennes 13:150 min—
Thu 15 OctRennes 13:20+5 min+5 min
Wed 14 OctRennes 13:150 min—
Tue 13 OctRennes 13:150 min—
Mon 12 OctRennes 13:150 min—
Fri 9 OctRennes 13:150 min—
Thu 8 OctRennes 14:00+45 min+45 min