Train NS 6628 Dordrecht – Arnhem Centraal

Dordrecht 08:58 → Arnhem Centraal 11:04 Daily 2 h 06 min · 23 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Arnhem Zuid at 11:14 0 min

  1. Dordrecht08:58
  2. Breda09:23
  3. Tilburg Universiteit09:40
  4. Rosmalen10:09
  5. Wijchen10:31
  6. Arnhem Zuid10:59
  7. Arnhem Centraal11:04

Next service: tomorrow 08:58 from Dordrecht · Sun 15 Nov

Next departure 08:58 tomorrow · Dordrecht
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 21 full · 1 partial · 8 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 28 full · 1 partial · 60 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: +1 min

Last 30 days

Arrival delay at Arnhem Centraal, in minutes. One bar per run.

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

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 100% · 29
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=5
  • 100% T n=5
  • 100% F n=3
  • 100% S n=6
  • 100% S n=4

Stops and timetable

Timetable of the latest run from the operator’s GTFS (23 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:58on time on time
09:01≈ on time ≈ on time
09:09 / 09:12≈ on time ≈ on time
09:19≈ on time ≈ on time
09:23 / 09:25≈ on time ≈ on time
09:32≈ on time ≈ on time
09:36≈ on time ≈ on time
09:40≈ on time ≈ +1 min
09:43 / 09:44≈ on time ≈ +1 min
10:00 / 10:02≈ on time ≈ +1 min
10:05≈ on time ≈ +1 min
10:09≈ on time ≈ +1 min
10:16≈ on time ≈ +1 min
10:20≈ on time ≈ +1 min
10:26≈ on time ≈ +1 min
10:31≈ on time ≈ +1 min
10:36≈ on time ≈ +1 min
10:39≈ on time ≈ +1 min
10:43 / 10:47≈ on time ≈ +1 min
10:50≈ on time ≈ +1 min
10:55≈ on time ≈ +1 min
10:59≈ on time ≈ +1 min
11:04on 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
Sat 14 NovArnhem Zuid 11:14Partial coverage0 min—
Fri 13 NovArnhem Zuid 11:14+1 min—
Thu 12 NovArnhem Zuid 11:140 min—
Wed 11 NovArnhem Zuid 11:14+1 min+1 min
Tue 10 NovArnhem Zuid 11:14+2 min+2 min
Mon 9 NovArnhem Zuid 11:140 min—
Sun 8 NovNijmegen Goffert 10:54+1 min+2 min
Sat 7 NovArnhem Zuid 11:140 min+3 min
Fri 6 NovArnhem Zuid 11:14No data—
Thu 5 NovArnhem Zuid 11:140 min—
Wed 4 NovArnhem Zuid 11:14+1 min+1 min
Tue 3 NovArnhem Zuid 11:14No data—
Mon 2 NovArnhem Zuid 11:19No data—
Sun 1 NovNijmegen Goffert 10:530 min—
Sat 31 OctNijmegen Goffert 10:530 min—
Fri 30 OctNijmegen Goffert 10:530 min—
Thu 29 OctNijmegen Goffert 10:530 min—
Wed 28 OctNijmegen Goffert 11:020 min—
Tue 27 OctNijmegen Goffert 10:530 min—
Mon 26 OctNijmegen Goffert 10:53No data—
Sun 25 OctNijmegen Goffert 10:57No data—
Sat 24 OctArnhem Zuid 11:140 min—
Fri 23 OctArnhem Zuid 11:16No data—
Thu 22 OctArnhem Zuid 11:140 min—
Wed 21 OctArnhem Zuid 11:160 min—
Tue 20 OctArnhem Zuid 11:14No data—
Mon 19 OctArnhem Zuid 11:140 min—
Sun 18 OctNijmegen Goffert 10:53+1 min+1 min
Sat 17 OctArnhem Zuid 11:140 min—
Fri 16 OctArnhem Zuid 11:14No data—