Train NS 21416 Eindhoven Centraal – Dordrecht

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

✓ Today’s run finished

Today, last fix heading to — at 02:39 0 min

Eindhoven Centraal01:42
Tilburg02:03
Breda02:18
Dordrecht02:37

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

Full trip card

Next departure 01:42 Friday · Eindhoven Centraal

On-time · 30 days

86%

6/7 runs under 3 min

RT coverage: 7 full · 0 partial · 1 no data

On-time · 90 days

86%

6/7 runs under 3 min

RT coverage: 7 full · 0 partial · 1 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

Sat 10 Oct Max en route +7 min · last fix heading to — +7 min

Distribution · 90 days

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

Early 0% · 0
On time 86% · 6
3–10 min 14% · 1
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
80% S n=5
100% S n=2

Stops and timetable

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

Last 90 days, 7 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.

Stop	Sched.	Usually	9 days in 10
Eindhoven Centraal	01:42	on time	+1 min
Tilburg	02:03 / 02:05	≈ on time	≈ +2 min
Breda	02:18 / 02:20	≈ on time	≈ +3 min
Dordrecht	02:37	on time	+4 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

Date	Last stop	Final	Max
Sat 7 Nov	— 02:39	0 min	—
Sat 31 Oct	— 02:06	0 min	—
Sun 25 Oct	— 02:52	0 min	—
Sat 24 Oct	— 02:53	0 min	—
Sun 18 Oct	— 02:13	No data	—
Sat 17 Oct	— 02:53	0 min	+1 min
Sun 11 Oct	— 02:59	+2 min	+2 min
Sat 10 Oct	— 02:59	+7 min	+7 min