P61 841617 Aulnoye-Aymeries – Hirson

View line P61

Aulnoye-Aymeries 19:42 → Hirson 20:17 Wed, Sat, Sun 0 h 35 min · 6 stops SNCF

It does not run today

Last recorded run: Wednesday 11 November 0 min

Next service: tomorrow 19:42 from Aulnoye-Aymeries · Sat 14 Nov

Next departure 19:42 tomorrow · Aulnoye-Aymeries
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 30 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 Hirson, in minutes. One bar per run.

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

Worst days

  • Wed 16 Sept Max en route +30 min · last fix heading to StopPoint:OCETrain TER-8729506 +30 min
  • Sun 6 Sept Max en route +5 min · last fix heading to StopPoint:OCETrain TER-8729506 +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 3% · 1

On-time by weekday

  • — M n=0
  • — T n=0
  • 86% W n=7
  • — T n=0
  • — F n=0
  • 100% S n=10
  • 92% S n=13

Stops and timetable

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

Last 90 days, 31 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
19:42on time on time
19:52 / 19:53≈ on time ≈ on time
19:58 / 19:59≈ on time ≈ on time
20:05 / 20:06≈ on time ≈ on time
20:10 / 20:11≈ on time ≈ on time
20:17on 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 11 NovHirson 20:180 min—
Sun 8 NovHirson 20:180 min—
Sat 7 NovHirson 20:180 min—
Sun 1 NovHirson 20:180 min—
Sat 31 OctHirson 20:190 min—
Sun 25 OctHirson 20:180 min—
Sat 24 OctHirson 20:180 min—
Sun 18 OctHirson 20:180 min—
Sat 17 OctHirson 20:180 min—
Sun 11 OctHirson 20:180 min—
Sat 10 OctHirson 20:180 min—
Sun 4 OctStopPoint:OCETrain TE~d0b11be0 20:190 min—
Wed 30 SeptStopPoint:OCETrain TER-8729506 20:160 min—
Sun 27 SeptStopPoint:OCETrain TER-8729506 20:160 min—
Sun 20 SeptStopPoint:OCETrain TER-8729506 20:170 min—
Sat 19 SeptStopPoint:OCETrain TER-8729506 20:160 min+15 min
Wed 16 SeptStopPoint:OCETrain TER-8729506 20:16+30 min+30 min
Sun 13 SeptStopPoint:OCETrain TER-8729506 20:160 min+25 min
Sat 12 SeptStopPoint:OCETrain TER-8729506 20:160 min+25 min
Wed 9 SeptStopPoint:OCETrain TER-8729506 20:160 min—
Sun 6 SeptStopPoint:OCETrain TER-8729506 20:16+5 min+5 min
Sat 5 SeptStopPoint:OCETrain TER-8729506 20:160 min—
Wed 2 SeptStopPoint:OCETrain TER-8729506 20:170 min—
Sun 30 AugStopPoint:OCETrain TER-8729506 20:160 min—
Sat 29 AugStopPoint:OCETrain TER-8729506 20:160 min—
Wed 26 AugStopPoint:OCETrain TER-8729506 20:160 min—
Sun 23 AugStopPoint:OCETrain TER-8729506 20:160 min—
Sat 22 AugStopPoint:OCETrain TER-8729506 20:160 min—
Wed 19 AugStopPoint:OCETrain TER-8729506 20:160 min—
Sun 16 AugStopPoint:OCETrain TER-8729506 20:160 min—