K2 880602 Briançon – Gap

View line K2

Briançon 06:52 → Gap 08:10 Mon, Tue, Wed, Thu, Fri 1 h 18 min · 6 stops SNCF

Running now · updated 08:00

Between Embrun and Chorges +15 min

Estimated arrival at Gap 08:25 08:10 · 67 km/h

  1. Briançon06:52
  2. L'Argentière les Écrins07:03
  3. Mont-Dauphin - Guillestre07:14
  4. Embrun07:29
  5. Chorges07:55
  6. Gap08:10

Today it is running worse than usual: typical arrival delay is 0 min; 90% of the last 21 runs arrived on time.

On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 20 full · 1 partial · 0 no data
On-time · 90 days
88%
21/24 runs under 3 min
RT coverage: 23 full · 1 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Gap, in minutes. One bar per run.

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

Worst days

  • Fri 16 Oct Max en route +20 min · last fix heading to Gap +20 min
  • Fri 6 Nov Max en route +20 min · last fix heading to Chorges +15 min
  • Wed 7 Oct Max en route +5 min · last fix heading to Gap +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 21
  • 3–10 min 4% · 1
  • 10–30 min 8% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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:52on time on timePassed
07:03 / 07:05≈ on time ≈ +1 minPassed
07:14 / 07:16≈ on time ≈ +1 minPassed
07:29 / 07:36≈ on time ≈ +2 minPassed
07:55 / 07:57≈ on time ≈ +1 minNext
08:10on 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 NovChorges 07:59Partial coverage+15 min+20 min
Wed 4 NovGap 08:090 min—
Tue 3 NovGap 08:090 min+5 min
Mon 2 NovGap 08:090 min—
Fri 30 OctGap 08:110 min—
Thu 29 OctGap 08:110 min—
Wed 28 OctGap 08:110 min—
Tue 27 OctGap 08:110 min—
Mon 26 OctGap 08:110 min—
Fri 23 OctGap 08:110 min—
Thu 22 OctGap 08:110 min—
Wed 21 OctGap 08:110 min—
Tue 20 OctGap 08:110 min—
Mon 19 OctGap 08:110 min—
Fri 16 OctGap 08:31+20 min+20 min
Thu 15 OctGap 08:110 min—
Wed 14 OctGap 08:110 min—
Tue 13 OctGap 08:110 min—
Mon 12 OctGap 08:110 min—
Fri 9 OctGap 08:110 min—
Thu 8 OctGap 08:110 min—
Wed 7 OctGap 08:17+5 min+5 min
Tue 6 OctGap 08:110 min+5 min
Mon 5 OctStopPoint:OCETrain TE~ccbf101a 08:120 min—