P10 854661 Guingamp – Lannion

View line P10

Guingamp 11:01 → Lannion 11:32 Sat 0 h 31 min · 3 stops SNCF

It does not run today

Last recorded run: Saturday 14 November 0 min

Next service: Saturday 11:01 from Guingamp · Sat 21 Nov

Next departure 11:01 Saturday · Guingamp
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 17 full · 0 partial · 2 no data
On-time · 90 days
94%
31/33 runs under 3 min
RT coverage: 33 full · 0 partial · 2 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 Lannion, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 6 Nov Max en route +5 min · last fix heading to Lannion +5 min
  • Sat 26 Sept Max en route +5 min · last fix heading to StopPoint:OCETrain TER-8747322 +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 94% · 31
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 75% F n=4
  • 90% S n=10
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (3 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
11:01on time on time
11:15 / 11:16≈ on time ≈ on time
11:32on 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
Sat 14 NovLannion 11:330 min—
Sat 7 NovLannion 11:330 min—
Fri 6 NovLannion 11:24+5 min+5 min
Thu 5 NovLannion 11:19No data—
Wed 4 NovLannion 11:190 min—
Tue 3 NovLannion 11:190 min—
Mon 2 NovLannion 11:190 min—
Sat 31 OctLannion 11:330 min—
Fri 30 OctLannion 11:190 min—
Thu 29 OctLannion 11:190 min—
Wed 28 OctLannion 11:190 min—
Tue 27 OctLannion 11:190 min—
Mon 26 OctLannion 11:190 min—
Sat 24 OctLannion 11:330 min—
Fri 23 OctLannion 11:19No data—
Thu 22 OctLannion 11:190 min—
Wed 21 OctLannion 11:190 min—
Tue 20 OctLannion 11:200 min—
Mon 19 OctLannion 11:190 min—
Sat 17 OctLannion 11:330 min—
Fri 16 OctLannion 11:190 min—
Thu 15 OctLannion 11:190 min—
Wed 14 OctLannion 11:190 min—
Tue 13 OctLannion 11:190 min—
Mon 12 OctLannion 11:200 min—
Sat 10 OctLannion 11:330 min—
Fri 9 OctLannion 11:200 min+5 min
Thu 8 OctLannion 11:190 min—
Wed 7 OctLannion 11:190 min—
Tue 6 OctLannion 11:190 min—