Train NS 6644 Dordrecht – Arnhem Centraal

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

✓ Today’s run finished

Today, last fix heading to Arnhem Zuid at 15:14 No data

  1. Dordrecht12:58
  2. Breda13:22
  3. Tilburg Universiteit13:40
  4. Rosmalen14:09
  5. Wijchen14:31
  6. Arnhem Zuid14:59
  7. Arnhem Centraal15:04

Next service: tomorrow 12:58 from Dordrecht · Sat 7 Nov

Next departure 12:58 tomorrow · Dordrecht
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 9 full · 6 partial · 15 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 9 full · 9 partial · 71 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 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

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

  • Early 0% · 0
  • On time 100% · 18
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=3
  • 100% T n=2
  • 100% F n=2
  • 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, 18 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
12:58on time on time
13:01≈ on time ≈ on time
13:09 / 13:10≈ on time ≈ on time
13:17≈ on time ≈ on time
13:22 / 13:24≈ on time ≈ on time
13:32≈ on time ≈ on time
13:36≈ on time ≈ on time
13:40≈ on time ≈ on time
13:43 / 13:44≈ on time ≈ on time
14:00 / 14:02≈ on time ≈ on time
14:05≈ on time ≈ on time
14:09≈ on time ≈ on time
14:16≈ on time ≈ on time
14:20≈ on time ≈ on time
14:26≈ on time ≈ on time
14:31≈ on time ≈ on time
14:36≈ on time ≈ on time
14:39≈ on time ≈ on time
14:43 / 14:47≈ on time ≈ on time
14:50≈ on time ≈ on time
14:55≈ on time ≈ on time
14:59≈ on time ≈ on time
15:04on 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 NovArnhem Zuid 15:14No data—
Thu 5 NovArnhem Zuid 15:14No data—
Wed 4 NovArnhem Zuid 15:14Partial coverage0 min—
Tue 3 NovArnhem Zuid 15:18No data—
Mon 2 NovArnhem Zuid 15:14No data—
Sun 1 NovNijmegen Goffert 14:54+1 min—
Sat 31 OctNijmegen Goffert 14:530 min—
Fri 30 OctNijmegen Goffert 14:530 min—
Thu 29 OctNijmegen Goffert 14:530 min—
Wed 28 OctNijmegen Goffert 14:530 min—
Tue 27 OctNijmegen Goffert 14:540 min—
Mon 26 OctNijmegen Goffert 14:53No data—
Sun 25 OctNijmegen Goffert 14:57No data—
Sat 24 OctArnhem Zuid 15:140 min—
Fri 23 OctNijmegen 15:34No data—
Thu 22 OctArnhem Zuid 15:14No data—
Wed 21 OctArnhem Zuid 15:19No data—
Tue 20 OctArnhem Zuid 15:14No data—
Mon 19 OctArnhem Zuid 15:15Partial coverage0 min—
Sun 18 OctNijmegen Goffert 14:530 min+2 min
Sat 17 OctArnhem Zuid 15:15No data—
Fri 16 OctArnhem Zuid 15:14No data—
Thu 15 OctArnhem Zuid 15:25No data—
Wed 14 OctArnhem Zuid 15:14No data—
Tue 13 OctArnhem Zuid 15:18Partial coverage0 min—
Mon 12 OctArnhem Zuid 15:14No data—
Sun 11 OctNijmegen Goffert 14:530 min—
Sat 10 OctArnhem Zuid 15:14Partial coverage0 min—
Fri 9 OctArnhem Zuid 15:14Partial coverage0 min—
Thu 8 OctArnhem Zuid 15:14Partial coverage0 min—