Train NS 6690 Dordrecht – Breda

Dordrecht 00:18 → Breda 00:41 Fri, Sat, Sun 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:44 0 min

  1. Dordrecht00:18
  2. Dordrecht Zuid00:21
  3. Lage Zwaluwe00:28
  4. Breda-Prinsenbeek00:36
  5. Breda00:41

Next service: tomorrow 00:18 from Dordrecht · Sun 8 Nov

Next departure 00:18 tomorrow · Dordrecht
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 8 full · 2 partial · 3 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 8 full · 2 partial · 12 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 Breda, 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

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

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

On-time by weekday

  • 100% M n=3
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=5
  • 100% S n=2

Stops and timetable

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

Last 90 days, 10 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
00:18on time on time
00:21≈ on time ≈ on time
00:28 / 00:29≈ on time ≈ on time
00:36≈ on time ≈ on time
00:41on 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 7 Nov— 01:440 min—
Mon 2 NovBreda-Prinsenbeek 00:49Partial coverage0 min—
Sun 1 Nov— 01:410 min—
Sat 31 Oct— 01:410 min—
Mon 26 OctBreda-Prinsenbeek 00:50No data—
Sun 25 Oct— 01:43No data—
Sat 24 Oct— 01:420 min—
Mon 19 OctBreda-Prinsenbeek 00:510 min—
Sun 18 OctTilburg 01:41No data—
Sat 17 Oct— 01:410 min—
Mon 12 OctBreda-Prinsenbeek 00:50Partial coverage0 min—
Sun 11 Oct— 01:420 min—
Sat 10 Oct— 01:410 min—
Mon 5 OctBreda-Prinsenbeek 00:50No data—
Mon 28 SeptBreda-Prinsenbeek 00:50No data—
Mon 21 SeptBreda-Prinsenbeek 00:50No data—
Mon 14 SeptBreda-Prinsenbeek 00:50No data—
Mon 7 SeptBreda-Prinsenbeek 01:16No data—
Mon 31 AugBreda-Prinsenbeek 00:50No data—
Mon 24 AugBreda-Prinsenbeek 00:51No data—
Mon 17 AugBreda-Prinsenbeek 00:51No data—
Mon 10 AugBreda-Prinsenbeek 00:50No data—