L6 96752 Pougny-Chancy – Bellegarde-sur-Valserine

View line L6

Pougny-Chancy 16:24 → Bellegarde-sur-Valserine 16:37 Mon, Tue, Wed, Thu, Fri 0 h 13 min · 2 stops SNCF

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 16:24 from Pougny-Chancy · Thu 19 Nov

Next departure 16:24 today · Pougny-Chancy
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
94%
31/33 runs under 3 min
RT coverage: 33 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Bellegarde-sur-Valserine, 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 5 Nov Max en route +30 min · last fix heading to Bellegarde-sur-Valserine +30 min
  • Wed 28 Oct Max en route +5 min · last fix heading to Bellegarde-sur-Valserine +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 31
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 3% · 1

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 86% W n=7
  • 83% T n=6
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 33 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
16:24on time on time
16:37on 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
Wed 18 NovBellegarde-sur-Valserine 16:380 min—
Tue 17 NovBellegarde-sur-Valserine 16:380 min—
Mon 16 NovBellegarde-sur-Valserine 16:380 min—
Fri 13 NovBellegarde-sur-Valserine 16:380 min—
Thu 12 NovBellegarde-sur-Valserine 16:380 min—
Wed 11 NovBellegarde-sur-Valserine 16:380 min+5 min
Tue 10 NovBellegarde-sur-Valserine 16:380 min—
Mon 9 NovBellegarde-sur-Valserine 16:380 min—
Fri 6 NovBellegarde-sur-Valserine 16:380 min—
Thu 5 NovBellegarde-sur-Valserine 17:08+30 min+30 min
Wed 4 NovBellegarde-sur-Valserine 16:380 min—
Tue 3 NovBellegarde-sur-Valserine 16:380 min—
Mon 2 NovBellegarde-sur-Valserine 16:380 min—
Fri 30 OctBellegarde-sur-Valserine 16:380 min—
Thu 29 OctBellegarde-sur-Valserine 16:380 min—
Wed 28 OctBellegarde-sur-Valserine 16:43+5 min+5 min
Tue 27 OctBellegarde-sur-Valserine 16:380 min—
Mon 26 OctBellegarde-sur-Valserine 16:380 min—
Fri 23 OctBellegarde-sur-Valserine 16:380 min—
Thu 22 OctBellegarde-sur-Valserine 16:380 min—
Wed 21 OctBellegarde-sur-Valserine 16:380 min—
Tue 20 OctBellegarde-sur-Valserine 16:380 min—
Mon 19 OctBellegarde-sur-Valserine 16:380 min+5 min
Fri 16 OctBellegarde-sur-Valserine 16:390 min—
Thu 15 OctBellegarde-sur-Valserine 16:380 min—
Wed 14 OctBellegarde-sur-Valserine 16:380 min—
Tue 13 OctBellegarde-sur-Valserine 16:380 min—
Mon 12 OctBellegarde-sur-Valserine 16:380 min—
Fri 9 OctBellegarde-sur-Valserine 16:380 min—
Thu 8 OctBellegarde-sur-Valserine 16:380 min—