Train NS 6413 Eindhoven Centraal – Weert

Eindhoven Centraal 06:17 → Weert 06:40 Mon, Tue, Wed, Thu, Fri 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Maarheeze at 06:49 No data

  1. Eindhoven Centraal06:17
  2. Geldrop06:22
  3. Heeze06:26
  4. Maarheeze06:33
  5. Weert06:40

Next service: Monday 06:17 from Eindhoven Centraal · Mon 9 Nov

Next departure 06:17 Monday · Eindhoven Centraal
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 15 full · 5 partial · 2 no data
On-time · 90 days
86%
19/22 runs under 3 min
RT coverage: 17 full · 5 partial · 42 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Weert, 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 30 Oct Max en route +7 min · last fix heading to Maarheeze +7 min
  • Tue 27 Oct Max en route +7 min · last fix heading to Maarheeze +6 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Maarheeze +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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
06:17on time on time
06:22≈ on time ≈ +1 min
06:26≈ on time ≈ +2 min
06:33≈ +1 min ≈ +3 min
06:40+1 min +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

DateLast stopFinalMax
Fri 6 NovMaarheeze 06:49No data—
Thu 5 NovMaarheeze 06:49Partial coverage0 min—
Wed 4 NovMaarheeze 06:52+4 min+4 min
Tue 3 NovMaarheeze 06:49+2 min+2 min
Mon 2 NovMaarheeze 06:49No data—
Fri 30 OctMaarheeze 06:54+7 min+7 min
Thu 29 OctMaarheeze 06:50Partial coverage+2 min+2 min
Wed 28 OctMaarheeze 06:49+2 min+2 min
Tue 27 OctMaarheeze 06:54+6 min+7 min
Mon 26 OctMaarheeze 06:470 min—
Fri 23 OctMaarheeze 06:49+2 min+2 min
Thu 22 OctMaarheeze 06:47Partial coverage0 min—
Wed 21 OctMaarheeze 06:48+1 min—
Tue 20 OctMaarheeze 06:48+1 min—
Mon 19 OctMaarheeze 06:48+1 min—
Fri 16 OctMaarheeze 06:470 min—
Thu 15 OctMaarheeze 06:47Partial coverage0 min—
Wed 14 OctMaarheeze 06:480 min—
Tue 13 OctMaarheeze 06:49+1 min+2 min
Mon 12 OctMaarheeze 06:50+2 min+3 min
Fri 9 OctMaarheeze 06:470 min—
Thu 8 OctMaarheeze 06:47Partial coverage0 min—
Wed 7 OctMaarheeze 06:51+2 min+4 min
Tue 6 OctMaarheeze 06:470 min—
Mon 5 OctMaarheeze 06:48No data—
Fri 2 OctMaarheeze 06:49No data—
Thu 1 OctMaarheeze 06:49No data—
Wed 30 SeptMaarheeze 06:49No data—
Tue 29 SeptMaarheeze 06:48No data—
Mon 28 SeptMaarheeze 06:48No data—