P1 855721 Morlaix – Brest

View line P1

Morlaix 12:13 → Brest 12:56 0 h 43 min · 7 stops SNCF

Not running right now

Last recorded run: Friday 6 November 0 min

On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 15 full · 0 partial · 1 no data
On-time · 90 days
98%
43/44 runs under 3 min
RT coverage: 44 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: 0 min

Last 30 days

Arrival delay at Brest, 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 5 Oct Max en route +15 min · last fix heading to Brest +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 43
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 44 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:13on time on time
12:27 / 12:28≈ on time ≈ on time
12:34 / 12:35≈ on time ≈ on time
12:39 / 12:40≈ on time ≈ on time
12:43 / 12:44≈ on time ≈ on time
12:49 / 12:50≈ on time ≈ on time
12:56on 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 6 NovBrest 12:570 min—
Thu 5 NovBrest 12:570 min—
Wed 4 NovBrest 12:570 min—
Tue 3 NovBrest 12:580 min—
Mon 2 NovBrest 12:570 min—
Fri 30 OctBrest 12:570 min—
Thu 29 OctBrest 12:570 min—
Wed 28 OctBrest 12:570 min—
Tue 27 OctBrest 12:570 min—
Mon 26 OctBrest 12:570 min—
Fri 23 OctBrest 12:57No data—
Thu 22 OctBrest 12:570 min—
Wed 21 OctBrest 12:570 min—
Tue 20 OctBrest 12:580 min—
Mon 19 OctBrest 12:570 min—
Fri 16 OctBrest 12:570 min—
Thu 15 OctBrest 12:570 min—
Wed 14 OctBrest 12:570 min—
Tue 13 OctBrest 12:570 min—
Mon 12 OctBrest 12:570 min—
Fri 9 OctBrest 12:570 min—
Thu 8 OctBrest 12:570 min—
Wed 7 OctBrest 12:570 min—
Tue 6 OctBrest 12:570 min—
Mon 5 OctBrest 13:12+15 min+15 min
Fri 25 SeptStopPoint:OCETrain TER-8747400 12:550 min—
Thu 24 SeptStopPoint:OCETrain TER-8747400 12:550 min—
Wed 23 SeptStopPoint:OCETrain TER-8747400 12:550 min—
Tue 22 SeptStopPoint:OCETrain TER-8747400 12:550 min—
Mon 21 SeptStopPoint:OCETrain TER-8747400 12:550 min—