C2 856040 Messac - Guipry → Rennes

View line C2

Messac - Guipry 12:29 → Rennes 13:07 Mon, Tue, Wed, Thu, Fri 0 h 38 min · 9 stops SNCF

TER 856040 Messac - Guipry–Rennes: final delay under 3 min on 18 of its 18 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 21:07 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 12:29 from Messac - Guipry · Mon 23 Nov

Next departure 12:29 tomorrow · Messac - Guipry
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 18 full · 0 partial · 1 no data
On-time · 90 days
100%
48/48 runs under 3 min
RT coverage: 47 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 48
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 100% T n=10
  • 100% W n=9
  • 100% T n=9
  • 100% F n=10
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 48 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:29on time on time
12:34 / 12:35≈ on time ≈ on time
12:38 / 12:39≈ on time ≈ on time
12:42 / 12:43≈ on time ≈ on time
12:47 / 12:48≈ on time ≈ on time
12:53 / 12:54≈ on time ≈ on time
12:56 / 12:57≈ on time ≈ on time
13:00 / 13:01≈ on time ≈ on time
13:07on 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 NovRennes 13:090 min—
Thu 19 NovRennes 13:080 min—
Wed 18 NovRennes 13:080 min—
Tue 17 NovRennes 13:080 min—
Mon 16 NovRennes 13:090 min—
Fri 13 NovRennes 13:080 min—
Thu 12 NovRennes 13:080 min—
Tue 10 NovRennes 13:080 min—
Mon 9 NovRennes 13:090 min—
Fri 6 NovRennes 13:080 min—
Thu 5 NovRennes 13:08No data—
Wed 4 NovRennes 13:080 min—
Tue 3 NovRennes 13:080 min—
Mon 2 NovRennes 13:080 min—
Fri 30 OctRennes 13:080 min—
Thu 29 OctRennes 13:080 min—
Wed 28 OctRennes 13:080 min—
Tue 27 OctRennes 13:080 min—
Mon 26 OctRennes 13:080 min—
Fri 23 OctRennes 13:080 min—
Thu 22 OctRennes 13:080 min—
Wed 21 OctRennes 13:080 min—
Tue 20 OctRennes 13:090 min—
Mon 19 OctRennes 13:080 min—
Fri 16 OctRennes 13:080 min—
Thu 15 OctRennes 13:080 min—
Wed 14 OctRennes 13:080 min—
Tue 13 OctRennes 13:080 min—
Mon 12 OctRennes 13:080 min—
Fri 9 OctRennes 13:080 min—