Train NS 16581 Eindhoven Centraal – Deurne

Eindhoven Centraal 23:06 → Deurne 23:27 Wed, Thu, Sun 0 h 21 min · 6 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Thursday 5 November No data

Next service: Sunday 23:06 from Eindhoven Centraal · Sun 8 Nov

Next departure 23:06 Sunday · Eindhoven Centraal
On-time · 30 days
50%
3/6 runs under 3 min
RT coverage: 4 full · 2 partial · 5 no data
On-time · 90 days
43%
3/7 runs under 3 min
RT coverage: 5 full · 2 partial · 14 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +2 min
P90
+9min
9 in 10 runs arrive with less than this
30 days: +9 min

Last 30 days

Arrival delay at Deurne, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 11 Oct Max en route +12 min · last fix heading to Helmond +12 min
  • Thu 8 Oct Max en route +7 min · last fix heading to — +7 min
  • Wed 7 Oct Max en route +6 min · last fix heading to — +5 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Helmond Brouwhuis +3 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 43% · 3
  • 3–10 min 43% · 3
  • 10–30 min 14% · 1
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • 75% W n=4
  • 0% T n=1
  • — F n=0
  • — S n=0
  • 0% S n=2

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 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.

StopSched.Usually 9 days in 10
23:06on time on time
23:12≈ on time ≈ +2 min
23:15≈ on time ≈ +3 min
23:19≈ on time ≈ +4 min
23:22≈ on time ≈ +5 min
23:27on time +6 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
Thu 5 Nov— 23:29No data—
Wed 4 Nov— 23:290 min—
Wed 28 Oct— 23:280 min—
Sun 25 OctHelmond Brouwhuis 23:38No data—
Thu 22 Oct— 23:28No data—
Wed 21 Oct— 23:29No data—
Sun 18 OctHelmond Brouwhuis 23:41Partial coverage+3 min+4 min
Thu 15 Oct— 23:28No data—
Wed 14 Oct— 23:280 min—
Sun 11 OctHelmond 23:49Partial coverage+12 min+12 min
Thu 8 Oct— 23:35+7 min+7 min
Wed 7 Oct— 23:34+5 min+6 min
Sun 4 OctHelmond Brouwhuis 23:38No data—
Sun 27 SeptHelmond Brouwhuis 23:37No data—
Sun 20 SeptHelmond Brouwhuis 23:42No data—
Sun 13 SeptHelmond Brouwhuis 23:37No data—
Sun 6 SeptHelmond Brouwhuis 23:37No data—
Sun 30 AugHelmond Brouwhuis 23:37No data—
Sun 23 AugHelmond Brouwhuis 23:37No data—
Sun 16 AugHelmond Brouwhuis 23:38No data—
Sun 9 AugHelmond Brouwhuis 23:37No data—