C2 856012 Messac - Guipry – Rennes

View line C2

Messac - Guipry 07:14 → Rennes 07:51 Mon, Tue, Wed, Thu, Fri 0 h 37 min · 8 stops SNCF

✓ Today’s run finished

Today it reached Rennes at 07:51 0 min

  1. Messac - Guipry07:14
  2. Pléchâtel07:21
  3. Saint-Senoux - Pléchâtel07:25
  4. Bruz07:37
  5. Ker Lann07:40
  6. Saint-Jacques-de-la-Lande07:44
  7. Rennes07:51

Next service: tomorrow 07:14 from Messac - Guipry · Fri 20 Nov

Next departure 07:14 tomorrow · Messac - Guipry
On-time · 30 days
79%
15/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
78%
28/36 runs under 3 min
RT coverage: 36 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: +6 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

  • Tue 10 Nov Max en route +10 min · last fix heading to Rennes +10 min
  • Wed 21 Oct Max en route +15 min · last fix heading to Rennes +10 min
  • Mon 24 Aug Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8715994 +10 min
  • Mon 16 Nov Max en route +5 min · last fix heading to Rennes +5 min
  • Fri 13 Nov Max en route +5 min · last fix heading to Rennes +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 28
  • 3–10 min 14% · 5
  • 10–30 min 8% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 63% M n=8
  • 71% T n=7
  • 71% W n=7
  • 100% T n=7
  • 86% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 36 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
07:14on time +5 min
07:21 / 07:22≈ on time ≈ +5 min
07:25 / 07:26≈ on time ≈ +5 min
07:29 / 07:30≈ on time ≈ +5 min
07:37 / 07:38≈ on time ≈ +5 min
07:40 / 07:41≈ on time ≈ +5 min
07:44 / 07:45≈ on time ≈ +5 min
07:51on 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 19 NovRennes 07:520 min—
Wed 18 NovRennes 07:520 min—
Mon 16 NovRennes 07:57+5 min+5 min
Fri 13 NovRennes 07:57+5 min+5 min
Thu 12 NovRennes 07:520 min—
Tue 10 NovRennes 08:02+10 min+10 min
Mon 9 NovRennes 07:520 min—
Fri 6 NovRennes 07:520 min—
Thu 5 NovRennes 07:52No data—
Wed 4 NovRennes 07:520 min—
Tue 3 NovRennes 07:520 min—
Mon 2 NovRennes 07:520 min—
Fri 30 OctRennes 07:520 min—
Thu 29 OctRennes 07:520 min—
Wed 28 OctRennes 07:520 min—
Tue 27 OctRennes 07:520 min—
Mon 26 OctRennes 07:520 min—
Fri 23 OctRennes 07:520 min—
Thu 22 OctRennes 07:520 min—
Wed 21 OctRennes 08:02+10 min+15 min
Tue 20 OctRennes 07:520 min—
Mon 19 OctRennes 07:520 min—
Fri 16 OctRennes 07:530 min—
Thu 15 OctRennes 07:520 min—
Wed 14 OctRennes 07:57+5 min+5 min
Tue 13 OctRennes 07:57+5 min+5 min
Mon 12 OctRennes 07:57+5 min+5 min
Fri 9 OctRennes 07:530 min—
Thu 8 OctRennes 07:520 min—
Wed 7 OctRennes 07:530 min—