Train NS 6629 Nijmegen → Dordrecht

Nijmegen 08:50 → Dordrecht 10:32 Daily 1 h 42 min · 19 stops NS (Nederlandse Spoorwegen)

Running now · updated 09:45

Position estimated from the timetable

Heading to Dordrecht 0 min

Estimated arrival at Dordrecht 10:32 · 74 km/h

  1. Nijmegen08:50
  2. Wijchen09:01
  3. Oss West09:16
  4. 's-Hertogenbosch09:30
  5. Tilburg Reeshof09:55
  6. Breda-Prinsenbeek10:13
  7. Dordrecht10:32

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 25 runs arrived on time.

On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 22 full · 3 partial · 5 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 30 full · 5 partial · 54 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 35 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
08:50on time on time
08:53≈ on time ≈ on time
08:56≈ on time ≈ on time
09:01≈ on time ≈ on time
09:06≈ on time ≈ on time
09:12 / 09:13≈ on time ≈ on time
09:16≈ on time ≈ on time
09:23≈ on time ≈ on time
09:27≈ on time ≈ on time
09:30 / 09:32≈ on time ≈ on time
09:46 / 09:48≈ on time ≈ on time
09:51≈ on time ≈ on time
09:55≈ on time ≈ on time
09:59≈ on time ≈ on time
10:06 / 10:09≈ on time ≈ on time
10:13≈ on time ≈ on time
10:20≈ on time ≈ on time
10:28≈ on time ≈ on time
10:32on 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
Sat 21 NovTilburg 09:44Partial coverage0 min—
Fri 20 NovDordrecht Zuid 10:420 min—
Thu 19 NovDordrecht Zuid 10:420 min—
Wed 18 NovDordrecht Zuid 10:430 min—
Tue 17 NovDordrecht Zuid 10:420 min+3 min
Mon 16 NovDordrecht Zuid 10:420 min—
Sun 15 NovDordrecht Zuid 10:430 min—
Sat 14 NovDordrecht Zuid 10:430 min—
Fri 13 NovDordrecht Zuid 10:420 min—
Thu 12 NovDordrecht Zuid 10:420 min—
Wed 11 NovDordrecht Zuid 10:420 min—
Tue 10 NovDordrecht Zuid 10:42+1 min+1 min
Mon 9 NovDordrecht Zuid 10:420 min—
Sun 8 NovDordrecht 10:480 min—
Sat 7 NovDordrecht 10:49+1 min+3 min
Fri 6 NovDordrecht Zuid 10:42No data—
Thu 5 NovDordrecht Zuid 10:42No data—
Wed 4 NovDordrecht Zuid 10:420 min—
Tue 3 NovDordrecht Zuid 10:42No data—
Mon 2 NovDordrecht Zuid 10:420 min—
Sun 1 NovDordrecht Zuid 10:420 min—
Sat 31 OctDordrecht Zuid 10:42Partial coverage0 min—
Fri 30 OctDordrecht Zuid 10:420 min—
Thu 29 OctDordrecht Zuid 10:420 min—
Wed 28 OctDordrecht Zuid 10:420 min—
Tue 27 OctDordrecht Zuid 10:420 min—
Mon 26 OctDordrecht Zuid 10:420 min—
Sun 25 OctDordrecht Zuid 10:43No data—
Sat 24 OctDordrecht Zuid 10:42Partial coverage0 min+3 min
Fri 23 OctDordrecht Zuid 10:42No data—