Train NS 6627 Arnhem Centraal – Dordrecht

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 07:57 from Arnhem Centraal · Thu 5 Nov

Next departure 07:57 today · Arnhem Centraal
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 12 full · 9 partial · 8 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 12 full · 10 partial · 66 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 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 +7 min · last fix heading to Dordrecht Zuid +3 min

Distribution · 90 days

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

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

On-time by weekday

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