Train NS 21412 Eindhoven Centraal – Dordrecht

Eindhoven Centraal 00:42 → Dordrecht 01:37 Fri, Sat 0 h 55 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

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

  1. Eindhoven Centraal00:42
  2. Tilburg01:03
  3. Breda01:18
  4. Dordrecht01:37

Next service: Friday 00:42 from Eindhoven Centraal · Fri 13 Nov

Next departure 00:42 Friday · Eindhoven Centraal
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 8 full · 0 partial · 1 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 8 full · 0 partial · 1 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 8 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:42on time on time
01:03 / 01:05≈ on time ≈ on time
01:18 / 01:20≈ on time ≈ on time
01:37on 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—
Sun 1 Nov— 01:530 min—
Sat 31 Oct— 01:520 min—
Sun 25 Oct— 01:590 min—
Sat 24 Oct— 01:530 min—
Sun 18 OctBreda 01:52No data—
Sat 17 Oct— 01:520 min—
Sun 11 Oct— 01:55+1 min—
Sat 10 Oct— 01:520 min—