Train NS 6631 Arnhem Centraal – Dordrecht

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

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 08:57 from Arnhem Centraal · Sat 7 Nov

Next departure 08:57 today · Arnhem Centraal
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 14 full · 3 partial · 12 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 15 full · 5 partial · 68 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 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 +12 min · last fix heading to Dordrecht Zuid +12 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Dordrecht Zuid +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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:57on time on time
09:02≈ on time ≈ on time
09:06≈ on time ≈ on time
09:10≈ on time ≈ on time
09:15 / 09:18≈ on time ≈ on time
09:21≈ on time ≈ on time
09:24≈ on time ≈ on time
09:28≈ on time ≈ on time
09:34≈ on time ≈ on time
09:40≈ on time ≈ on time
09:43≈ on time ≈ on time
09:50≈ on time ≈ on time
09:54≈ on time ≈ on time
09:58 / 10:01≈ on time ≈ on time
10:15 / 10:17≈ on time ≈ on time
10:20≈ on time ≈ on time
10:24≈ on time ≈ on time
10:28≈ on time ≈ on time
10:35 / 10:39≈ on time ≈ on time
10:43≈ on time ≈ on time
10:50≈ on time ≈ on time
10:58≈ on time ≈ on time
11:02on 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
Fri 6 NovDordrecht Zuid 11:12No data—
Thu 5 NovDordrecht Zuid 11:12No data—
Wed 4 NovDordrecht Zuid 11:14Partial coverage+3 min+4 min
Tue 3 NovDordrecht Zuid 11:13No data—
Mon 2 NovDordrecht Zuid 11:120 min—
Sun 1 NovDordrecht Zuid 11:130 min—
Sat 31 OctDordrecht Zuid 11:120 min—
Fri 30 OctDordrecht Zuid 11:120 min—
Thu 29 OctDordrecht Zuid 11:12No data—
Wed 28 OctDordrecht Zuid 11:13No data—
Tue 27 OctDordrecht Zuid 11:200 min—
Mon 26 OctDordrecht Zuid 11:120 min—
Sun 25 OctDordrecht Zuid 11:12No data—
Sat 24 OctDordrecht Zuid 11:120 min—
Fri 23 OctDordrecht Zuid 11:12No data—
Thu 22 OctDordrecht Zuid 11:250 min—
Wed 21 OctDordrecht Zuid 11:15No data—
Tue 20 OctDordrecht Zuid 11:13Partial coverage0 min—
Mon 19 OctDordrecht Zuid 11:120 min—
Sun 18 OctDordrecht Zuid 11:120 min—
Sat 17 OctDordrecht Zuid 11:120 min—
Fri 16 OctDordrecht Zuid 11:12No data—
Thu 15 OctDordrecht Zuid 11:13No data—
Wed 14 OctDordrecht Zuid 11:12No data—
Tue 13 OctDordrecht Zuid 11:12No data—
Mon 12 OctDordrecht Zuid 11:120 min—
Sun 11 OctDordrecht Zuid 11:120 min—
Sat 10 OctDordrecht Zuid 11:120 min—
Fri 9 OctDordrecht Zuid 11:26Partial coverage+12 min+12 min
Thu 8 OctDordrecht Zuid 11:12Partial coverage0 min—