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

View line P4

Briançon 06:05 → Romans - Bourg-de-Péage 10:24 Mon, Tue, Wed, Thu, Fri, Sun 4 h 19 min · 15 stops SNCF

Running now · updated 07:04

Position estimated from the timetable

Between Embrun and Chorges No data

Estimated arrival at Romans - Bourg-de-Péage 10:24 · 6 km/h

  1. Briançon06:05
  2. Montdauphin-Guillestre06:28
  3. Embrun06:43
  4. Chorges07:04
  5. Gap07:26
  6. Luc-en-Diois08:32
  7. Romans - Bourg-de-Péage10:24
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
98%
61/62 runs under 3 min
RT coverage: 62 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

  • Thu 17 Sept Max en route +5 min · last fix heading to Laufen +5 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 98% · 61
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=10
  • 100% W n=9
  • 89% T n=9
  • 100% F n=7
  • 100% S n=9
  • 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
06:05on time on timePassed
06:17 / 06:18≈ on time ≈ on timePassed
06:28 / 06:29≈ on time ≈ on timePassed
06:43 / 06:44≈ on time ≈ on timePassed
07:04 / 07:13≈ on time ≈ on timeNext
07:26 / 07:29≈ on time ≈ on time
07:52 / 07:55≈ on time ≈ on time
08:32 / 08:34≈ on time ≈ +1 min
08:51 / 08:53≈ on time ≈ +1 min
09:14 / 09:15≈ on time ≈ +1 min
09:28 / 09:30≈ on time ≈ +1 min
09:47 / 09:49≈ on time ≈ +1 min
10:01 / 10:08≈ on time ≈ +1 min
10:15 / 10:17≈ on time ≈ +1 min
10:24on time +1 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
Tue 17 NovChorges 07:04Partial coverageNo data—
Mon 16 NovLaufen 18:380 min—
Sun 15 NovLaufen 18:380 min—
Sat 14 NovLaufen 18:380 min—
Fri 13 NovLaufen 18:380 min—
Thu 12 NovLaufen 18:39+3 min+3 min
Wed 11 NovLaufen 18:39+1 min+1 min
Tue 10 NovLaufen 18:380 min—
Mon 9 NovLaufen 18:380 min—
Sun 8 NovLaufen 18:38−1 min—
Sat 7 NovLaufen 18:370 min—
Fri 6 NovLaufen 18:380 min—
Thu 5 NovLaufen 18:380 min—
Wed 4 NovLaufen 18:39+3 min+3 min
Tue 3 NovLaufen 18:380 min—
Mon 2 NovLaufen 18:380 min—
Sun 1 NovLaufen 18:380 min—
Sat 31 OctLaufen 18:37−1 min—
Fri 30 OctLaufen 18:380 min—
Thu 29 OctLaufen 18:39+1 min—
Wed 28 OctLaufen 18:39+1 min—
Tue 27 OctLaufen 18:380 min—
Mon 26 OctLaufen 18:39+1 min—
Sun 25 OctLaufen 18:370 min—
Sat 24 OctLaufen 18:380 min—
Fri 23 OctLaufen 18:38No data—
Thu 22 OctLaufen 18:380 min—
Wed 21 OctLaufen 18:380 min—
Tue 20 OctLaufen 18:40+2 min+2 min
Mon 19 OctLaufen 18:370 min—