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

View line P4

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

Running now · updated 12:35

Position estimated from the timetable

Between Veynes-Devoluy and Luc-en-Diois No data

Estimated arrival at Romans - Bourg-de-Péage 14:50 · 68 km/h

  1. Briançon10:47
  2. Montdauphin-Guillestre11:13
  3. Gap12:05
  4. Veynes-Devoluy12:27
  5. Luc-en-Diois13:06
  6. Saillans13:46
  7. Romans - Bourg-de-Péage14:50
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
94%
58/62 runs under 3 min
RT coverage: 62 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Romans - Bourg-de-Péage, 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 7 Oct Max en route +24 min · last fix heading to Zwingen +24 min
  • Tue 20 Oct Max en route +5 min · last fix heading to Laufen +5 min
  • Mon 12 Oct Max en route +5 min · last fix heading to Laufen +5 min
  • Mon 16 Nov Max en route +7 min · last fix heading to Laufen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 58
  • 3–10 min 5% · 3
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 92% T n=12
  • 89% W n=9
  • 100% T n=8
  • 100% F n=9
  • 100% S n=7
  • 100% S n=9

Stops and timetable

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

Last 90 days, 62 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
10:47on time on timePassed
10:59 / 11:03≈ on time ≈ on timePassed
11:13 / 11:15≈ on time ≈ on timePassed
11:28 / 11:32≈ on time ≈ on timePassed
11:51 / 11:52≈ on time ≈ on timePassed
12:05 / 12:07≈ on time ≈ on timePassed
12:27 / 12:30≈ on time ≈ +1 minPassed
13:06 / 13:07≈ on time ≈ +1 minNext
13:24 / 13:25≈ on time ≈ +1 min
13:46 / 13:47≈ on time ≈ +1 min
13:59 / 14:01≈ on time ≈ +1 min
14:18 / 14:19≈ on time ≈ +2 min
14:30 / 14:33≈ on time ≈ +2 min
14:40 / 14:43≈ on time ≈ +2 min
14:50on 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 NovLuc-en-Diois 12:34Partial coverageNo data—
Wed 18 NovLaufen 19:370 min—
Tue 17 NovLaufen 19:39+2 min+2 min
Mon 16 NovLaufen 19:42+4 min+7 min
Sun 15 NovLaufen 19:380 min—
Sat 14 NovLaufen 19:39+1 min+5 min
Fri 13 NovLaufen 19:380 min—
Thu 12 NovLaufen 19:370 min—
Wed 11 NovLaufen 19:380 min—
Tue 10 NovLaufen 19:380 min—
Mon 9 NovLaufen 19:380 min—
Sun 8 NovLaufen 19:380 min—
Sat 7 NovLaufen 19:370 min—
Fri 6 NovLaufen 19:380 min—
Thu 5 NovLaufen 19:380 min—
Wed 4 NovLaufen 19:380 min—
Tue 3 NovLaufen 19:380 min—
Mon 2 NovLaufen 19:380 min—
Sun 1 NovLaufen 19:380 min—
Sat 31 OctLaufen 19:380 min—
Fri 30 OctLaufen 19:380 min—
Thu 29 OctLaufen 19:380 min—
Wed 28 OctLaufen 19:41+3 min+3 min
Tue 27 OctLaufen 19:39+1 min+6 min
Mon 26 OctLaufen 19:380 min—
Sun 25 OctLaufen 19:380 min—
Sat 24 OctLaufen 19:380 min—
Fri 23 OctLaufen 19:380 min—
Thu 22 OctLaufen 19:380 min—
Wed 21 OctLaufen 19:380 min—