Train NS 6671 Arnhem Centraal – Dordrecht

Arnhem Centraal 18:57 → Dordrecht 21:02 Daily 2 h 05 min · 23 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 18:57 from Arnhem Centraal · Fri 6 Nov

Next departure 18:57 today · Arnhem Centraal
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 15 full · 1 partial · 12 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 18 full · 1 partial · 41 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: +1 min

Last 30 days

Arrival delay at Dordrecht, in minutes. One bar per run.

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

Worst days

  • Fri 9 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=2
  • 100% W n=3
  • 100% T n=4
  • 67% F n=3
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 19 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
18:57on time on time
19:02≈ on time ≈ on time
19:06≈ on time ≈ on time
19:10≈ on time ≈ on time
19:15 / 19:18≈ on time ≈ on time
19:21≈ on time ≈ on time
19:24≈ on time ≈ on time
19:28≈ on time ≈ +1 min
19:34≈ on time ≈ +1 min
19:40≈ on time ≈ +1 min
19:43≈ on time ≈ +1 min
19:50≈ on time ≈ +1 min
19:54≈ on time ≈ +1 min
19:58 / 20:01≈ on time ≈ +1 min
20:15 / 20:17≈ on time ≈ +1 min
20:20≈ on time ≈ +1 min
20:24≈ on time ≈ +1 min
20:28≈ on time ≈ +1 min
20:35 / 20:39≈ on time ≈ +1 min
20:43≈ on time ≈ +1 min
20:50≈ on time ≈ +1 min
20:58≈ on time ≈ +1 min
21:02on time +1 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
Thu 5 Nov— 21:040 min—
Wed 4 Nov— 21:04+2 min+2 min
Tue 3 Nov— 21:03No data—
Mon 2 Nov— 21:03No data—
Sun 1 NovDordrecht Zuid 21:120 min+2 min
Sat 31 OctDordrecht Zuid 21:120 min—
Thu 29 Oct— 20:510 min—
Wed 28 Oct— 21:060 min—
Tue 27 Oct— 20:420 min—
Mon 26 OctRosmalen 21:03No data—
Sun 25 OctDordrecht Zuid 21:16No data—
Sat 24 OctDordrecht Zuid 21:120 min—
Fri 23 OctWijchen 21:030 min—
Thu 22 Oct— 21:030 min—
Wed 21 Oct— 21:04No data—
Tue 20 Oct— 21:03No data—
Mon 19 Oct— 19:44No data—
Sun 18 OctDordrecht Zuid 21:120 min—
Sat 17 OctDordrecht Zuid 21:12No data—
Fri 16 Oct's-Hertogenbosch Oost 21:03Partial coverage0 min—
Thu 15 Oct— 21:03No data—
Wed 14 OctOss West 21:03No data—
Tue 13 Oct— 21:04No data—
Mon 12 Oct— 21:03No data—
Sun 11 OctDordrecht Zuid 21:120 min—
Sat 10 OctDordrecht Zuid 21:120 min—
Fri 9 Oct— 21:09+4 min+4 min
Thu 8 Oct— 21:030 min—
Wed 7 Oct— 21:040 min—
Tue 6 Oct— 20:360 min—