Train NS 6461 Tilburg Universiteit – Weert

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 17:34 from Tilburg Universiteit · Fri 6 Nov

Next departure 17:34 today · Tilburg Universiteit
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 2 full · 13 partial · 14 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 2 full · 16 partial · 70 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
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

  • Sun 11 Oct Max en route +8 min · last fix heading to Maarheeze +7 min
  • Sun 1 Nov Max en route +6 min · last fix heading to Maarheeze +5 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=3
  • 100% T n=3
  • 100% W n=2
  • 100% T n=2
  • 100% F n=2
  • 100% S n=3
  • 33% 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
17:34on time +1 min
17:38 / 17:39— —
17:45— —
17:52 / 17:53— —
17:59— —
18:05— —
18:09 / 18:17— —
18:22— —
18:26— —
18:33— —
18:40— —

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
Thu 5 NovEindhoven Strijp-S 18:39No data—
Wed 4 NovEindhoven Strijp-S 18:42No data—
Tue 3 NovEindhoven Strijp-S 18:39Partial coverage0 min—
Mon 2 NovEindhoven Strijp-S 18:39Partial coverage+1 min+1 min
Sun 1 NovMaarheeze 18:54+5 min+6 min
Sat 31 OctMaarheeze 18:49+1 min—
Fri 30 OctMaarheeze 18:47No data—
Thu 29 OctBest 18:41Partial coverage0 min—
Wed 28 OctEindhoven Strijp-S 18:42Partial coverage+1 min—
Tue 27 OctEindhoven Strijp-S 18:44No data—
Mon 26 OctEindhoven Strijp-S 18:42Partial coverage0 min—
Sun 25 OctMaarheeze 18:48No data—
Sat 24 OctMaarheeze 18:48Partial coverage0 min—
Fri 23 OctMaarheeze 18:47Partial coverage+3 min+3 min
Thu 22 OctMaarheeze 18:47No data—
Wed 21 OctMaarheeze 18:47No data—
Tue 20 OctEindhoven Centraal 18:49Partial coverage0 min—
Mon 19 OctMaarheeze 18:47No data—
Sun 18 OctMaarheeze 18:48Partial coverage+1 min—
Sat 17 OctMaarheeze 18:52No data—
Fri 16 OctMaarheeze 18:48No data—
Thu 15 OctHeeze 18:46No data—
Wed 14 OctMaarheeze 18:42No data—
Tue 13 OctMaarheeze 18:47No data—
Mon 12 OctMaarheeze 18:47No data—
Sun 11 OctMaarheeze 18:55Partial coverage+7 min+8 min
Sat 10 OctMaarheeze 18:48Partial coverage+1 min—
Fri 9 OctMaarheeze 18:47Partial coverage+1 min—
Thu 8 OctBest 18:43Partial coverage+1 min—
Wed 7 OctEindhoven Strijp-S 18:19Partial coverage0 min—