K52 846416 Dunkerque → Arras

View line K52

Dunkerque 08:32 → Arras 10:03 Mon, Tue, Wed, Thu, Fri 1 h 31 min · 14 stops SNCF

TER 846416 Dunkerque–Arras: final delay under 3 min on 11 of its 14 runs with data in the last 30 days (79%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 02:56 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 08:32 from Dunkerque · Mon 23 Nov

Next departure 08:32 tomorrow · Dunkerque
On-time · 30 days
79%
11/14 runs under 3 min
RT coverage: 14 full · 0 partial · 5 no data
On-time · 90 days
83%
24/29 runs under 3 min
RT coverage: 29 full · 0 partial · 5 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+11min
9 in 10 runs arrive with less than this
30 days: +14 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 +90 min · last fix heading to Arras +90 min
  • Fri 6 Nov Max en route +15 min · last fix heading to Arras +15 min
  • Fri 30 Oct Max en route +15 min · last fix heading to Arras +15 min
  • Wed 18 Nov Max en route +15 min · last fix heading to Arras +10 min
  • Fri 16 Oct Max en route +5 min · last fix heading to Arras +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 24
  • 3–10 min 3% · 1
  • 10–30 min 10% · 3
  • 30+ min 3% · 1

On-time by weekday

  • 100% M n=7
  • 100% T n=4
  • 83% W n=6
  • 83% T n=6
  • 50% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 29 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
08:32on time on time
08:34 / 08:35≈ on time ≈ on time
08:40 / 08:41≈ on time ≈ +1 min
08:46 / 08:47≈ on time ≈ +1 min
08:52 / 08:53≈ on time ≈ +1 min
08:57 / 08:58≈ on time ≈ +2 min
09:05 / 09:07≈ on time ≈ +2 min
09:16 / 09:17≈ on time ≈ +3 min
09:22 / 09:23≈ on time ≈ +4 min
09:31 / 09:33≈ on time ≈ +4 min
09:37 / 09:38≈ on time ≈ +5 min
09:42 / 09:43≈ on time ≈ +5 min
09:48 / 09:50≈ on time ≈ +5 min
10:03on time +7 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 20 NovArras 10:050 min—
Thu 19 NovArras 10:040 min—
Wed 18 NovArras 10:14+10 min+15 min
Tue 17 NovArras 10:04No data—
Mon 16 NovArras 10:040 min+5 min
Fri 13 NovArras 10:04No data—
Thu 12 NovArras 10:040 min—
Tue 10 NovArras 10:04No data—
Mon 9 NovArras 10:040 min—
Fri 6 NovArras 10:19+15 min+15 min
Thu 5 NovArras 10:04No data—
Wed 4 NovArras 10:040 min—
Tue 3 NovArras 10:04No data—
Mon 2 NovArras 10:040 min—
Fri 30 OctArras 10:19+15 min+15 min
Thu 29 OctArras 10:040 min—
Wed 28 OctArras 10:040 min—
Tue 27 OctArras 10:040 min—
Mon 26 OctArras 10:040 min—
Fri 23 OctArras 10:040 min—
Thu 22 OctArras 11:24+90 min+90 min
Wed 21 OctArras 10:040 min—
Tue 20 OctArras 10:050 min—
Mon 19 OctArras 10:040 min—
Fri 16 OctArras 10:09+5 min+5 min
Thu 15 OctArras 10:040 min—
Wed 14 OctArras 10:040 min—
Tue 13 OctArras 10:040 min—
Mon 12 OctArras 10:050 min—
Fri 9 OctArras 10:050 min—