Train NS 6636 Dordrecht – Arnhem Centraal

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

Running now · updated 12:34

Heading to Arnhem Centraal No data

Estimated arrival at Arnhem Centraal 13:04 · 67 km/h

  1. Dordrecht10:58
  2. Breda11:22
  3. Tilburg Universiteit11:40
  4. Rosmalen12:09
  5. Wijchen12:31
  6. Nijmegen12:43
  7. Arnhem Centraal13:04
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 12 full · 5 partial · 13 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 12 full · 8 partial · 69 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

Worst days

  • Sun 11 Oct Max en route +7 min · last fix heading to Nijmegen Goffert +5 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 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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