TER 96613 Bellegarde-sur-Valserine – Genève

View line TER

Bellegarde-sur-Valserine 13:33 → Genève 14:12 Daily 0 h 39 min · 2 stops SBB CFF FFS

Running now · updated 14:10

Position estimated from the timetable

Between Bellegarde-sur-Valserine and Genève −1 min

Estimated arrival at Genève 14:12 · 49 km/h

  1. Bellegarde-sur-Valserine13:33
  2. Genève14:12

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

On-time · 30 days
92%
23/25 runs under 3 min
RT coverage: 25 full · 0 partial · 4 no data
On-time · 90 days
92%
35/38 runs under 3 min
RT coverage: 38 full · 0 partial · 5 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: +2 min

Last 30 days

Arrival delay at Genève, 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 8 Oct Max en route +35 min · last fix heading to Genève +35 min
  • Sun 25 Oct Max en route +50 min · last fix heading to Genève +32 min
  • Wed 4 Nov Max en route +16 min · last fix heading to Genève +16 min

Distribution · 90 days

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

  • Early 11% · 4
  • On time 82% · 31
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 5% · 2

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 83% W n=6
  • 50% T n=2
  • 100% F n=6
  • 100% S n=6
  • 86% S n=7

Stops and timetable

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

Last 90 days, 38 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
13:33on time on timePassed
14:12on time +3 minNext

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
Mon 16 NovGenève 14:09−1 min—
Sun 15 NovGenève 14:130 min—
Sat 14 NovGenève 14:130 min—
Fri 13 NovGenève 14:12−1 min+5 min
Thu 12 NovGenève 14:13+1 min—
Wed 11 NovGenève 14:14+2 min+5 min
Tue 10 NovGenève 14:14+2 min+2 min
Mon 9 NovGenève 14:13+1 min—
Sun 8 NovGenève 14:130 min—
Sat 7 NovGenève 14:130 min—
Fri 6 NovGenève 14:14+1 min—
Thu 5 NovGenève 14:13No data—
Wed 4 NovGenève 14:29+16 min+16 min
Mon 2 NovGenève 14:12−1 min—
Sun 1 NovGenève 14:130 min—
Sat 31 OctGenève 14:130 min—
Fri 30 OctGenève 14:130 min—
Thu 29 OctGenève 14:13No data—
Wed 28 OctGenève 14:13−1 min—
Tue 27 OctGenève 14:130 min—
Mon 26 OctGenève 14:14+1 min—
Sun 25 OctGenève 14:44+32 min+50 min
Sat 24 OctGenève 14:130 min—
Fri 23 OctGenève 14:120 min+5 min
Thu 22 OctGenève 14:13No data—
Wed 21 OctGenève 14:130 min—
Tue 20 OctGenève 14:130 min—
Mon 19 OctGenève 14:13No data—
Sun 18 OctGenève 14:13−1 min—
Sat 17 OctGenève 14:120 min—