Train NS 6492 Weert – Eindhoven Centraal

Weert 23:50 → Eindhoven Centraal 00: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 23:50 from Weert · Sat 7 Nov

Full trip card

Next departure 23:50 today · Weert

On-time · 30 days

91%

20/22 runs under 3 min

RT coverage: 20 full · 2 partial · 5 no data

On-time · 90 days

92%

23/25 runs under 3 min

RT coverage: 23 full · 2 partial · 15 no data

Typical delay

0min

Median at arrival, 90 days

30 days: 0 min

P90

+2min

9 in 10 runs arrive with less than this

30 days: +1 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 9 Oct Max en route +4 min · last fix heading to — +4 min
Fri 23 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

Early 0% · 0
On time 92% · 23
3–10 min 8% · 2
10–30 min 0% · 0
30+ min 0% · 0

On-time by weekday

100% M n=5
100% T n=4
100% W n=3
100% T n=3
60% F n=5
100% S n=2
100% S n=3

Stops and timetable

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

Last 90 days, 25 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
Weert	23:50	on time	on time
Maarheeze	23:56	≈ on time	≈ +1 min
Heeze	00:03	≈ on time	≈ +2 min
Geldrop	00:07	≈ on time	≈ +2 min
Eindhoven Centraal	00:13	on 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

Date	Last stop	Final	Max
Fri 6 Nov	— 00:14	0 min	—
Wed 4 Nov	— 00:14	0 min	—
Tue 3 Nov	— 00:23	0 min	—
Mon 2 Nov	— 00:14	0 min	—
Sun 1 Nov	Geldrop 00:22	+1 min	—
Sat 31 Oct	— 00:15	0 min	—
Fri 30 Oct	— 00:14	0 min	—
Thu 29 Oct	— 00:14	+1 min	—
Wed 28 Oct	— 00:14	No data	—
Tue 27 Oct	— 00:15	0 min	—
Mon 26 Oct	— 00:14	0 min	—
Sun 25 Oct	Geldrop 00:22	No data	—
Sat 24 Oct	— 00:17	No data	—
Fri 23 Oct	— 00:19	+4 min	+4 min
Wed 21 Oct	— 00:15	0 min	—
Tue 20 Oct	— 00:17	0 min	—
Mon 19 Oct	— 00:14	0 min	—
Sun 18 Oct	Geldrop 00:22Partial coverage	0 min	—
Sat 17 Oct	Geldrop 00:24	No data	—
Fri 16 Oct	— 00:14	0 min	—
Thu 15 Oct	— 00:16	0 min	—
Wed 14 Oct	— 00:14	0 min	—
Tue 13 Oct	— 00:15	No data	—
Mon 12 Oct	— 00:14	0 min	—
Sun 11 Oct	Geldrop 00:21Partial coverage	0 min	—
Sat 10 Oct	— 00:15	0 min	—
Fri 9 Oct	— 00:22	+4 min	+4 min
Thu 8 Oct	— 00:18	+2 min	+2 min
Tue 6 Oct	— 00:14	0 min	—
Mon 5 Oct	Geldrop 00:14	0 min	—