K52 846402 Hazebrouck – Arras

View line K52

Hazebrouck 10:08 → Arras 11:03 Mon, Tue, Wed, Thu, Fri 0 h 55 min · 8 stops SNCF

✓ Today’s run finished

Today it reached Arras at 11:13 +10 min

  1. Hazebrouck10:08
  2. Berguette - Isbergues10:18
  3. Lillers10:23
  4. Noeux-Les-Mines10:38
  5. Bully - Grenay10:43
  6. Lens10:49
  7. Arras11:03

Next service: Monday 10:08 from Hazebrouck · Mon 9 Nov

Next departure 10:08 Monday · Hazebrouck
On-time · 30 days
67%
14/21 runs under 3 min
RT coverage: 21 full · 0 partial · 1 no data
On-time · 90 days
67%
16/24 runs under 3 min
RT coverage: 24 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+17min
9 in 10 runs arrive with less than this
30 days: +10 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

Worst days

  • Thu 22 Oct Max en route +80 min · last fix heading to Arras +80 min
  • Mon 5 Oct Max en route +40 min · last fix heading to StopPoint:OCETrain TE~eb1be547 +40 min
  • Tue 27 Oct Max en route +20 min · last fix heading to Arras +20 min
  • Fri 6 Nov Max en route +10 min · last fix heading to Arras +10 min
  • Fri 30 Oct Max en route +10 min · last fix heading to Arras +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 67% · 16
  • 3–10 min 13% · 3
  • 10–30 min 13% · 3
  • 30+ min 8% · 2

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
10:08on time +9 min
10:18 / 10:19≈ on time ≈ +11 min
10:23 / 10:24≈ on time ≈ +12 min
10:32 / 10:34≈ on time ≈ +12 min
10:38 / 10:39≈ on time ≈ +13 min
10:43 / 10:44≈ on time ≈ +14 min
10:49 / 10:51≈ on time ≈ +15 min
11:03on time +17 min

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
Fri 6 NovArras 11:14+10 min+10 min
Thu 5 NovArras 11:09+5 min+5 min
Wed 4 NovArras 11:040 min—
Tue 3 NovArras 11:04No data—
Mon 2 NovArras 11:040 min—
Fri 30 OctArras 11:14+10 min+10 min
Thu 29 OctArras 11:040 min—
Wed 28 OctArras 11:040 min—
Tue 27 OctArras 11:24+20 min+20 min
Mon 26 OctArras 11:040 min—
Fri 23 OctArras 11:040 min—
Thu 22 OctArras 12:24+80 min+80 min
Wed 21 OctArras 11:040 min—
Tue 20 OctArras 11:040 min—
Mon 19 OctArras 11:050 min—
Fri 16 OctArras 11:040 min—
Thu 15 OctArras 11:09+5 min+5 min
Wed 14 OctArras 11:040 min—
Tue 13 OctArras 11:040 min—
Mon 12 OctArras 11:050 min—
Fri 9 OctArras 11:10+5 min+10 min
Thu 8 OctArras 11:040 min—
Wed 7 OctArras 11:040 min—
Tue 6 OctArras 11:040 min—
Mon 5 OctStopPoint:OCETrain TE~eb1be547 11:44+40 min+40 min