P10 854655 Guingamp – Lannion

View line P10

Guingamp 06:39 → Lannion 07:09 Mon, Tue, Wed, Thu, Fri 0 h 30 min · 3 stops SNCF

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 06:39 from Guingamp · Thu 5 Nov

Next departure 06:39 today · Guingamp
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 20 full · 0 partial · 1 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 22 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: +1 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

  • Mon 26 Oct Max en route +10 min · last fix heading to Lannion +10 min
  • Tue 27 Oct Max en route +5 min · last fix heading to Lannion +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 20
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 80% T n=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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
06:39on time on time
06:52 / 06:53≈ on time ≈ on time
07: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
Wed 4 NovLannion 07:090 min—
Tue 3 NovLannion 07:090 min—
Mon 2 NovLannion 07:090 min—
Fri 30 OctLannion 07:100 min—
Thu 29 OctLannion 07:100 min—
Wed 28 OctLannion 07:100 min—
Tue 27 OctLannion 07:15+5 min+5 min
Mon 26 OctLannion 07:20+10 min+10 min
Fri 23 OctLannion 07:10No data—
Thu 22 OctLannion 07:100 min—
Wed 21 OctLannion 07:100 min—
Tue 20 OctLannion 07:100 min—
Mon 19 OctLannion 07:100 min—
Fri 16 OctLannion 07:100 min—
Thu 15 OctLannion 07:100 min—
Wed 14 OctLannion 07:100 min—
Tue 13 OctLannion 07:100 min—
Mon 12 OctLannion 07:100 min—
Fri 9 OctLannion 07:110 min—
Thu 8 OctLannion 07:100 min—
Wed 7 OctLannion 07:100 min—
Tue 6 OctLannion 07:110 min—
Mon 5 OctStopPoint:OCETrain TE~c7c1b72d 07:110 min—