C3 854250 Montreuil-sur-Ille – Rennes

View line C3

Montreuil-sur-Ille 13:20 → Rennes 13:51 Mon, Tue, Wed, Thu, Fri 0 h 31 min · 7 stops SNCF

✓ Today’s run finished

Today it reached Rennes at 13:51 0 min

  1. Montreuil-sur-Ille13:20
  2. Saint-Médard-sur-Ille13:24
  3. Saint-Germain-sur-Ille13:28
  4. Chevaigné13:33
  5. Betton13:37
  6. Pontchaillou13:44
  7. Rennes13:51

Next service: tomorrow 13:20 from Montreuil-sur-Ille · Thu 19 Nov

Next departure 13:20 tomorrow · Montreuil-sur-Ille
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
96%
45/47 runs under 3 min
RT coverage: 47 full · 0 partial · 0 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

  • Mon 16 Nov Max en route +10 min · last fix heading to Rennes +10 min
  • Thu 22 Oct Max en route +10 min · last fix heading to Rennes +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 45
  • 3–10 min 0% · 0
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=12
  • 100% W n=11
  • 91% T n=11
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

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