Train NS 6677 Nijmegen – Dordrecht

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

It has not run yet today

Last recorded run: Monday 2 November 0 min

Next service: today 20:50 from Nijmegen · Thu 5 Nov

Next departure 20:50 today · Nijmegen
On-time · 30 days
83%
10/12 runs under 3 min
RT coverage: 9 full · 3 partial · 13 no data
On-time · 90 days
86%
12/14 runs under 3 min
RT coverage: 11 full · 3 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

Worst days

  • Fri 23 Oct Max en route +9 min · last fix heading to — +9 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Dordrecht Zuid +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 12
  • 3–10 min 14% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 100% W n=1
  • 100% T n=1
  • 67% F n=3
  • 100% S n=2
  • 67% S n=3

Stops and timetable

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

Last 90 days, 14 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
20:50on time on time
20:53≈ on time ≈ on time
20:56≈ on time ≈ on time
21:01≈ on time ≈ on time
21:06≈ on time ≈ on time
21:12 / 21:13≈ on time ≈ on time
21:16≈ on time ≈ on time
21:23≈ on time ≈ +1 min
21:27≈ on time ≈ +1 min
21:30 / 21:32≈ on time ≈ +1 min
21:46 / 21:48≈ on time ≈ +1 min
21:51≈ on time ≈ +1 min
21:55≈ on time ≈ +1 min
21:59≈ on time ≈ +1 min
22:06 / 22:09≈ on time ≈ +1 min
22:13≈ on time ≈ +1 min
22:20≈ on time ≈ +1 min
22:28≈ on time ≈ +2 min
22:32on 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
Mon 2 Nov— 22:330 min—
Sun 1 NovDordrecht Zuid 22:44Partial coverage+2 min+6 min
Sat 31 OctDordrecht Zuid 22:420 min—
Fri 30 Oct— 22:33No data—
Wed 28 Oct— 22:33No data—
Tue 27 Oct— 22:39No data—
Mon 26 Oct— 22:59No data—
Sun 25 OctDordrecht Zuid 22:42No data—
Sat 24 OctDordrecht Zuid 22:42No data—
Fri 23 Oct— 22:48+9 min+9 min
Thu 22 Oct— 23:06No data—
Wed 21 Oct— 22:34No data—
Mon 19 Oct— 21:16No data—
Sun 18 OctDordrecht Zuid 22:46Partial coverage+4 min+4 min
Sat 17 OctDordrecht Zuid 22:52No data—
Fri 16 Oct— 22:330 min—
Thu 15 Oct— 22:38No data—
Wed 14 Oct— 22:33No data—
Tue 13 Oct— 22:34No data—
Mon 12 Oct— 22:330 min—
Sun 11 OctDordrecht Zuid 22:42Partial coverage0 min—
Sat 10 OctGilze-Rijen 22:340 min—
Fri 9 Oct— 22:330 min—
Thu 8 Oct— 22:330 min—
Wed 7 Oct— 22:34+2 min+2 min
Tue 6 Oct— 22:330 min—
Mon 5 Oct— 22:330 min—
Sun 4 OctDordrecht Zuid 22:43No data—
Sat 3 OctDordrecht Zuid 22:43No data—
Sun 27 SeptDordrecht Zuid 22:42No data—