Train NS 6646 Dordrecht → Nijmegen

Dordrecht 13:28 → Nijmegen 15:13 Daily 1 h 45 min · 19 stops NS (Nederlandse Spoorwegen)

NS 6646 Dordrecht–Nijmegen: final delay under 3 min on 23 of its 24 runs with data in the last 30 days (96%). Median final delay: 0 min. TrainsRadar data as of 23 Nov 2026, 00:03 (GMT+1).

It has not run yet today

Last recorded run: Sunday 22 November +1 min

Next service: today 13:28 from Dordrecht · Mon 23 Nov

Next departure 13:28 today · Dordrecht
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 22 full · 2 partial · 5 no data
On-time · 90 days
97%
35/36 runs under 3 min
RT coverage: 32 full · 4 partial · 52 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

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

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

Worst days

  • Tue 17 Nov Max en route +6 min · last fix heading to Arnhem Zuid +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 35
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 36 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
13:28on time on time
13:31≈ on time ≈ on time
13:39 / 13:40≈ on time ≈ on time
13:47≈ on time ≈ on time
13:52 / 13:54≈ on time ≈ on time
14:02≈ on time ≈ on time
14:06≈ on time ≈ +1 min
14:10≈ on time ≈ +1 min
14:13 / 14:14≈ on time ≈ +1 min
14:30 / 14:32≈ on time ≈ +1 min
14:35≈ on time ≈ +1 min
14:39≈ on time ≈ +1 min
14:46≈ on time ≈ +1 min
14:49≈ on time ≈ +1 min
14:55≈ on time ≈ +1 min
15:01≈ on time ≈ +1 min
15:05≈ on time ≈ +1 min
15:08≈ on time ≈ +1 min
15:13on time +2 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
Sun 22 NovNijmegen Goffert 15:23Partial coverage+1 min—
Sat 21 NovArnhem Zuid 15:440 min—
Fri 20 NovArnhem Zuid 15:44+3 min+7 min
Thu 19 NovArnhem Zuid 15:44+1 min—
Wed 18 NovArnhem Zuid 15:440 min—
Tue 17 NovArnhem Zuid 15:49+6 min+6 min
Mon 16 NovArnhem Zuid 15:550 min—
Sun 15 NovNijmegen Goffert 15:23+1 min+1 min
Sat 14 NovArnhem Zuid 15:440 min—
Fri 13 NovArnhem Zuid 15:44+2 min+2 min
Thu 12 NovArnhem Zuid 15:44+2 min+3 min
Wed 11 NovArnhem Zuid 15:440 min—
Tue 10 NovArnhem Zuid 15:440 min—
Mon 9 NovArnhem Zuid 15:450 min—
Sun 8 NovNijmegen Goffert 15:230 min—
Sat 7 NovArnhem Zuid 15:440 min—
Fri 6 NovArnhem Zuid 15:44No data—
Thu 5 NovArnhem Zuid 15:44No data—
Wed 4 NovArnhem Zuid 15:440 min—
Tue 3 NovArnhem Zuid 15:44No data—
Mon 2 NovArnhem Zuid 15:430 min—
Sun 1 NovNijmegen Goffert 15:26Partial coverage+2 min+2 min
Sat 31 OctNijmegen Goffert 15:23+1 min+1 min
Fri 30 OctNijmegen Goffert 15:250 min—
Thu 29 OctNijmegen Goffert 15:230 min—
Wed 28 OctNijmegen Goffert 15:230 min—
Tue 27 OctNijmegen Goffert 15:240 min—
Mon 26 OctNijmegen Goffert 15:23No data—
Sun 25 OctNijmegen Goffert 15:23No data—
Sat 24 OctArnhem Zuid 15:460 min—