Train NS 6484 Weert – Eindhoven Centraal

Weert 21:50 → Eindhoven Centraal 22:13 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 21:50 from Weert · Sat 7 Nov

Next departure 21:50 today · Weert
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 9 full · 3 partial · 14 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 13 full · 3 partial · 30 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Eindhoven Centraal, 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 23 Oct Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 100% W n=2
  • 100% T n=2
  • 75% F n=4
  • 100% S n=1
  • 100% S n=3

Stops and timetable

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

Last 90 days, 16 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
21:50on time on time
21:56≈ on time ≈ +1 min
22:03≈ on time ≈ +1 min
22:07≈ +1 min ≈ +1 min
22:13+1 min +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
Fri 6 Nov— 22:140 min—
Thu 5 Nov— 21:49No data—
Wed 4 Nov— 22:14+2 min+2 min
Mon 2 Nov— 22:140 min—
Sun 1 NovGeldrop 22:220 min—
Sat 31 OctGeldrop 22:21No data—
Thu 29 Oct— 22:140 min—
Wed 28 Oct— 22:14No data—
Tue 27 Oct— 22:14No data—
Mon 26 Oct— 22:15No data—
Sun 25 OctGeldrop 22:21No data—
Sat 24 OctGeldrop 22:45No data—
Fri 23 Oct— 22:25+6 min+6 min
Thu 22 Oct— 22:15No data—
Wed 21 Oct— 22:15No data—
Tue 20 Oct— 22:48No data—
Sun 18 OctGeldrop 22:21Partial coverage0 min—
Sat 17 OctGeldrop 22:22No data—
Fri 16 Oct— 22:18+2 min+2 min
Thu 15 Oct— 22:48No data—
Wed 14 Oct— 22:14No data—
Tue 13 Oct— 22:14No data—
Mon 12 Oct— 22:210 min—
Sun 11 OctGeldrop 22:21Partial coverage0 min—
Sat 10 OctHeeze 22:19Partial coverage+2 min+2 min
Fri 9 Oct— 22:15+2 min+2 min
Thu 8 Oct— 22:15+1 min+1 min
Wed 7 Oct— 22:16+1 min+1 min
Tue 6 Oct— 22:15+1 min—
Mon 5 Oct— 22:140 min—