Train NS 6421 Eindhoven Centraal – Weert

Eindhoven Centraal 08:17 → Weert 08:40 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November +12 min

Next service: today 08:17 from Eindhoven Centraal · Sun 8 Nov

Next departure 08:17 today · Eindhoven Centraal
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 16 full · 4 partial · 9 no data
On-time · 90 days
88%
21/24 runs under 3 min
RT coverage: 20 full · 4 partial · 64 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: +6 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

  • Sat 7 Nov Max en route +12 min · last fix heading to Maarheeze +12 min
  • Sun 11 Oct Max en route +9 min · last fix heading to Maarheeze +9 min
  • Sun 1 Nov Max en route +5 min · last fix heading to Maarheeze +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 21
  • 3–10 min 8% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=4
  • 100% T n=2
  • 100% F n=3
  • 80% S n=5
  • 33% S n=3

Stops and timetable

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

Last 90 days, 24 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
08:17on time on time
08:22≈ on time ≈ on time
08:26≈ on time ≈ +1 min
08:33≈ on time ≈ +2 min
08:40on time +2 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
Sat 7 NovMaarheeze 08:59Partial coverage+12 min+12 min
Fri 6 NovMaarheeze 08:48No data—
Thu 5 NovMaarheeze 08:48No data—
Wed 4 NovMaarheeze 08:48+1 min—
Tue 3 NovMaarheeze 08:490 min—
Mon 2 NovMaarheeze 08:490 min—
Sun 1 NovMaarheeze 08:50+5 min+5 min
Sat 31 OctMaarheeze 08:50+1 min+1 min
Fri 30 OctMaarheeze 08:480 min—
Thu 29 OctMaarheeze 08:480 min—
Wed 28 OctMaarheeze 08:490 min—
Tue 27 OctMaarheeze 08:490 min—
Mon 26 OctMaarheeze 08:480 min—
Sun 25 OctMaarheeze 08:47No data—
Sat 24 OctMaarheeze 08:49Partial coverage+1 min+2 min
Fri 23 OctMaarheeze 08:490 min—
Thu 22 OctMaarheeze 08:48No data—
Wed 21 OctMaarheeze 08:530 min—
Tue 20 OctMaarheeze 08:48No data—
Mon 19 OctMaarheeze 08:480 min—
Sun 18 OctMaarheeze 08:470 min—
Sat 17 OctMaarheeze 08:49Partial coverage+2 min+2 min
Fri 16 OctMaarheeze 08:48No data—
Thu 15 OctMaarheeze 08:49No data—
Wed 14 OctMaarheeze 08:49No data—
Tue 13 OctMaarheeze 08:53No data—
Mon 12 OctMaarheeze 08:520 min—
Sun 11 OctMaarheeze 08:56+9 min+9 min
Sat 10 OctMaarheeze 08:48Partial coverage+1 min—
Fri 9 OctMaarheeze 08:48+1 min—