K21 17596 Valence – Grenoble

View line K21

Valence 21:16 → Grenoble 22:28 Daily 1 h 12 min · 8 stops SNCF

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 21:16 from Valence · Fri 6 Nov

Next departure 21:16 today · Valence
On-time · 30 days
—
Too little data (2/14 runs with data)
RT coverage: 2 full · 0 partial · 12 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 9 full · 0 partial · 14 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 9
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • 100% F n=1
  • — S n=0
  • 100% S n=1

Stops and timetable

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

Last 90 days, 9 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
21:16on time +1 min
21:23 / 21:25≈ on time ≈ +1 min
21:33 / 21:35≈ on time ≈ on time
21:45 / 21:46≈ on time ≈ on time
21:53 / 21:55≈ on time ≈ on time
22:08 / 22:10≈ on time ≈ on time
22:15 / 22:17≈ on time ≈ on time
22:28on 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
Thu 5 NovGrenoble 22:29No data—
Wed 4 NovGrenoble 22:29No data—
Tue 3 NovGrenoble 22:29No data—
Mon 2 NovGrenoble 22:29No data—
Sun 1 NovChambéry-Challes-les-Eaux 23:19No data—
Sat 31 OctChambéry-Challes-les-Eaux 23:20No data—
Sun 25 OctChambéry-Challes-les-Eaux 23:20No data—
Sat 24 OctChambéry-Challes-les-Eaux 23:20No data—
Sun 18 OctChambéry-Challes-les-Eaux 23:20No data—
Sat 17 OctChambéry-Challes-les-Eaux 23:20No data—
Sun 11 OctChambéry-Challes-les-Eaux 23:20No data—
Sat 10 OctChambéry-Challes-les-Eaux 23:20No data—
Fri 9 OctBasel Bad Bf 06:060 min—
Thu 8 OctBasel Bad Bf 06:060 min—
Wed 7 OctBasel Bad Bf 06:060 min—
Tue 6 OctBasel Bad Bf 06:060 min—
Mon 5 OctBasel Bad Bf 06:070 min—
Sun 4 OctChambéry-Challes-les-Eaux 23:20No data—
Sat 3 OctChambéry-Challes-les-Eaux 23:21No data—
Sun 27 SeptAnnecy 21:140 min+1 min
Thu 13 AugAnnecy 23:110 min—
Wed 12 AugAnnecy 23:110 min—
Tue 11 AugAnnecy 23:110 min—