C4 855288 Rennes → Vitré

View line C4

Rennes 20:37 → Vitré 21:09 Mon, Tue, Wed, Thu, Fri 0 h 32 min · 6 stops SNCF

TER 855288 Rennes–Vitré: final delay under 3 min on 16 of its 18 runs with data in the last 30 days (89%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 07:27 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 20:37 from Rennes · Mon 23 Nov

Next departure 20:37 tomorrow · Rennes
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 18 full · 0 partial · 1 no data
On-time · 90 days
91%
30/33 runs under 3 min
RT coverage: 33 full · 0 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: +2 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

  • Wed 18 Nov Max en route +15 min · last fix heading to Vitré +15 min
  • Tue 17 Nov Max en route +5 min · last fix heading to Vitré +5 min
  • Thu 22 Oct Max en route +5 min · last fix heading to Vitré +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 30
  • 3–10 min 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 86% T n=7
  • 83% W n=6
  • 83% T n=6
  • 100% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 33 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
20:37on time on time
20:42 / 20:43≈ on time ≈ +1 min
20:47 / 20:48≈ on time ≈ +2 min
20:52 / 20:53≈ on time ≈ +2 min
20:56 / 20:57≈ on time ≈ +2 min
21:09on 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
Fri 20 NovVitré 21:090 min+5 min
Thu 19 NovVitré 21:090 min—
Wed 18 NovVitré 21:24+15 min+15 min
Tue 17 NovVitré 21:14+5 min+5 min
Mon 16 NovVitré 21:090 min—
Fri 13 NovVitré 21:090 min—
Thu 12 NovVitré 21:090 min—
Tue 10 NovVitré 21:090 min—
Mon 9 NovVitré 21:090 min—
Fri 6 NovVitré 21:090 min—
Thu 5 NovVitré 21:09No data—
Wed 4 NovVitré 21:090 min—
Tue 3 NovVitré 21:090 min—
Mon 2 NovVitré 21:090 min—
Fri 30 OctVitré 21:100 min—
Thu 29 OctVitré 21:100 min—
Wed 28 OctVitré 21:100 min—
Tue 27 OctVitré 21:100 min—
Mon 26 OctVitré 21:110 min—
Fri 23 OctVitré 21:110 min—
Thu 22 OctVitré 21:15+5 min+5 min
Wed 21 OctVitré 21:100 min+5 min
Tue 20 OctVitré 21:100 min—
Mon 19 OctVitré 21:100 min—
Fri 16 OctVitré 21:100 min—
Thu 15 OctVitré 21:100 min—
Wed 14 OctVitré 21:100 min—
Tue 13 OctVitré 21:100 min—
Mon 12 OctVitré 21:100 min—
Fri 9 OctVitré 21:100 min—