P4 17353 Romans - Bourg-de-Péage – Briançon

View line P4

Romans - Bourg-de-Péage 09:47 → Briançon 14:10 Mon, Tue, Wed, Thu, Fri, Sat 4 h 23 min · 15 stops SNCF

Running now · updated 13:44

Position estimated from the timetable

Between Embrun and Montdauphin-Guillestre No data

Estimated arrival at Briançon 14:10 · 41 km/h

  1. Romans - Bourg-de-Péage09:47
  2. Valence10:02
  3. Saillans10:48
  4. Luc-en-Diois11:30
  5. Embrun13:27
  6. Montdauphin-Guillestre13:44
  7. Briançon14:10
On-time · 30 days
90%
26/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
94%
68/72 runs under 3 min
RT coverage: 72 full · 0 partial · 5 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Briançon, in minutes. One bar per run.

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

Worst days

  • Wed 14 Oct Max en route +5 min · last fix heading to Olten +5 min
  • Tue 17 Nov Max en route +4 min · last fix heading to Olten +4 min
  • Wed 11 Nov Max en route +4 min · last fix heading to Olten +4 min
  • Mon 9 Nov Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 68
  • 3–10 min 6% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 92% T n=12
  • 83% W n=12
  • 100% T n=8
  • 100% F n=10
  • 100% S n=11
  • 100% S n=10

Stops and timetable

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

Last 90 days, 72 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 10Today
09:47on time on timePassed
09:53 / 09:54≈ on time ≈ on timePassed
10:02 / 10:04≈ on time ≈ on timePassed
10:15 / 10:17≈ on time ≈ on timePassed
10:34 / 10:36≈ on time ≈ on timePassed
10:48 / 10:50≈ on time ≈ +1 minPassed
11:11 / 11:13≈ on time ≈ +1 minPassed
11:30 / 11:32≈ on time ≈ +1 minPassed
12:09 / 12:32≈ on time ≈ +1 minPassed
12:52 / 12:55≈ on time ≈ +2 minPassed
13:07 / 13:09≈ on time ≈ +2 minPassed
13:27 / 13:31≈ on time ≈ +2 minPassed
13:44 / 13:46≈ on time ≈ +2 minNext
13:56 / 13:58≈ on time ≈ +2 min
14:10on time +2 min

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
Thu 19 NovMontdauphin-Guillestre 13:39Partial coverageNo data—
Wed 18 NovOlten 15:42+1 min+1 min
Tue 17 NovOlten 15:44+4 min+4 min
Mon 16 NovOlten 15:390 min—
Sun 15 NovTecknau 15:34+1 min—
Sat 14 NovTecknau 15:330 min—
Fri 13 NovOlten 15:42+1 min—
Thu 12 NovOlten 15:43+2 min+2 min
Wed 11 NovOlten 15:44+4 min+4 min
Tue 10 NovOlten 15:390 min—
Mon 9 NovOlten 15:44+3 min+3 min
Sun 8 NovOlten 15:42+1 min—
Sat 7 NovOlten 15:390 min—
Fri 6 NovOlten 15:42+1 min+1 min
Thu 5 NovOlten 15:390 min—
Wed 4 NovOlten 15:420 min—
Tue 3 NovOlten 15:390 min—
Mon 2 NovOlten 15:43+2 min+2 min
Sun 1 NovOlten 15:410 min—
Sat 31 OctOlten 15:410 min—
Fri 30 OctOlten 15:44+3 min+3 min
Thu 29 OctOlten 15:42+1 min+1 min
Wed 28 OctOlten 15:42+1 min—
Tue 27 OctOlten 15:410 min—
Mon 26 OctOlten 15:44+3 min+3 min
Sun 25 OctOlten 15:41+1 min—
Sat 24 OctOlten 15:42+1 min—
Fri 23 OctOlten 15:42+1 min+1 min
Thu 22 OctOlten 15:42+1 min—
Wed 21 OctOlten 15:410 min—