F32 865476 Niversac – Mussidan

View line F32

Niversac 12:39 → Mussidan 13:27 Mon, Tue, Wed, Thu, Fri, Sat 0 h 48 min · 9 stops SNCF

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 12:39 from Niversac · Fri 6 Nov

Next departure 12:39 today · Niversac
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 1 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 1 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 Mussidan, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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
12:39on time on time
12:43 / 12:44≈ on time ≈ on time
12:50 / 12:53≈ on time ≈ on time
12:57 / 12:58≈ on time ≈ on time
13:02 / 13:03≈ on time ≈ on time
13:09 / 13:10≈ on time ≈ on time
13:12 / 13:13≈ on time ≈ on time
13:17 / 13:18≈ on time ≈ on time
13:27on 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 NovMussidan 13:28No data—
Wed 4 NovMussidan 13:280 min—
Tue 3 NovMussidan 13:290 min—
Mon 2 NovMussidan 13:280 min—
Sat 31 OctMussidan 13:280 min—
Fri 30 OctMussidan 13:280 min—
Thu 29 OctMussidan 13:280 min—
Wed 28 OctMussidan 13:280 min—
Tue 27 OctMussidan 13:280 min—
Mon 26 OctMussidan 13:290 min—
Sat 24 OctMussidan 13:280 min—
Fri 23 OctMussidan 13:280 min—
Thu 22 OctMussidan 13:280 min—
Wed 21 OctMussidan 13:280 min—
Tue 20 OctMussidan 13:290 min—
Mon 19 OctMussidan 13:290 min—
Sat 17 OctMussidan 13:280 min—
Fri 16 OctMussidan 13:280 min—
Thu 15 OctMussidan 13:280 min—
Wed 14 OctMussidan 13:280 min—
Tue 13 OctMussidan 13:280 min—
Mon 12 OctMussidan 13:280 min—
Sat 10 OctMussidan 13:290 min—
Fri 9 OctMussidan 13:280 min—
Thu 8 OctMussidan 13:280 min—
Wed 7 OctMussidan 13:280 min—
Tue 6 OctMussidan 13:280 min—
Mon 5 OctStopPoint:OCETrain TE~0b364bea 13:280 min—