P22 848875 Amiens – Arras

View line P22

Amiens 13:43 → Arras 14:33 Wed, Sun 0 h 50 min · 8 stops SNCF

It does not run today

Last recorded run: Wednesday 11 November 0 min

Next service: Sunday 13:43 from Amiens · Sun 15 Nov

Next departure 13:43 Sunday · Amiens
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 5 full · 0 partial · 0 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 14 full · 0 partial · 7 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 Arras, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
13:43on time on time
13:53 / 13:54≈ on time ≈ on time
14:03 / 14:04≈ on time ≈ on time
14:11 / 14:12≈ on time ≈ on time
14:16 / 14:17≈ on time ≈ on time
14:21 / 14:22≈ on time ≈ on time
14:25 / 14:26≈ on time ≈ on time
14:33on 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 NovArras 14:340 min—
Sun 8 NovArras 14:340 min—
Sun 1 NovArras 14:340 min—
Sun 25 OctArras 14:340 min—
Sun 18 OctArras 14:340 min—
Sun 11 OctArras 14:340 min—
Sun 4 OctStopPoint:OCETrain TE~eb1be547 14:340 min—
Wed 30 SeptStopPoint:OCETrain TER-8734201 14:32No data—
Sun 27 SeptStopPoint:OCETrain TER-8734201 14:320 min—
Wed 23 SeptStopPoint:OCETrain TER-8734201 14:32No data—
Sun 20 SeptStopPoint:OCETrain TER-8734201 14:330 min—
Wed 16 SeptStopPoint:OCETrain TER-8734201 14:33No data—
Sun 13 SeptStopPoint:OCETrain TER-8734201 14:320 min—
Wed 9 SeptStopPoint:OCETrain TER-8734201 14:32No data—
Sun 6 SeptStopPoint:OCETrain TER-8734201 14:320 min—
Wed 2 SeptStopPoint:OCETrain TER-8734201 14:33No data—
Sun 30 AugStopPoint:OCETrain TER-8734201 14:320 min—
Wed 26 AugStopPoint:OCETrain TER-8734201 14:32No data—
Sun 23 AugStopPoint:OCETrain TER-8734201 14:320 min—
Wed 19 AugStopPoint:OCETrain TER-8734201 14:32No data—
Sun 16 AugStopPoint:OCETrain TER-8734201 14:330 min—