Train NS 6465 Tilburg Universiteit – Weert

Tilburg Universiteit 18:34 → Weert 19:40 Daily 1 h 06 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 18:34 from Tilburg Universiteit · Thu 5 Nov

Next departure 18:34 today · Tilburg Universiteit
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 8 full · 8 partial · 13 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 10 full · 8 partial · 50 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: +5 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 23 Oct Max en route +8 min · last fix heading to Heeze +8 min
  • Fri 9 Oct Max en route +7 min · last fix heading to Tilburg Universiteit +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 16
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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
18:34on time on time
18:38 / 18:39≈ on time ≈ +1 min
18:45≈ on time ≈ +1 min
18:52 / 18:53≈ on time ≈ +1 min
18:59≈ on time ≈ +1 min
19:05≈ on time ≈ +1 min
19:09 / 19:17≈ on time ≈ +1 min
19:22≈ on time ≈ +1 min
19:26≈ on time ≈ +1 min
19:33≈ on time ≈ +1 min
19:40on time +1 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
Wed 4 Nov— 19:42No data—
Tue 3 Nov— 19:42No data—
Mon 2 NovEindhoven Centraal 19:44Partial coverage0 min—
Sun 1 NovMaarheeze 19:490 min+1 min
Sat 31 OctMaarheeze 19:49+1 min—
Fri 30 OctBoxtel 19:31No data—
Thu 29 Oct— 19:420 min—
Wed 28 Oct— 19:470 min—
Tue 27 Oct— 19:48No data—
Mon 26 Oct— 19:420 min—
Sun 25 OctMaarheeze 19:49No data—
Sat 24 OctMaarheeze 19:50Partial coverage0 min—
Fri 23 OctHeeze 19:47Partial coverage+8 min+8 min
Thu 22 OctOisterwijk 19:44No data—
Wed 21 OctTilburg 19:44No data—
Tue 20 OctOisterwijk 19:17No data—
Mon 19 OctTilburg 19:42No data—
Sun 18 OctMaarheeze 19:49Partial coverage+1 min+1 min
Sat 17 OctMaarheeze 19:49No data—
Fri 16 OctMaarheeze 19:47No data—
Thu 15 Oct— 19:44No data—
Wed 14 OctMaarheeze 19:42No data—
Tue 13 OctTilburg 19:480 min—
Mon 12 OctOisterwijk 19:42Partial coverage0 min—
Sun 11 OctMaarheeze 19:48Partial coverage0 min+1 min
Sat 10 OctMaarheeze 19:49Partial coverage+2 min+2 min
Fri 9 OctTilburg Universiteit 19:47Partial coverage+7 min+7 min
Thu 8 Oct— 19:42+1 min+1 min
Wed 7 Oct— 19:47+2 min+2 min
Tue 6 Oct— 19:420 min—