Train NS 6431 Tilburg Universiteit – Weert

Tilburg Universiteit 10:04 → Weert 11:10 Daily 1 h 06 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +5 min

Next service: today 10:04 from Tilburg Universiteit · Thu 5 Nov

Next departure 10:04 today · Tilburg Universiteit
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 6 full · 10 partial · 12 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 6 full · 11 partial · 68 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Wed 4 Nov Max en route +5 min · last fix heading to Maarheeze +5 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
10:04on time on time
10:08 / 10:09≈ on time ≈ on time
10:15≈ on time ≈ on time
10:22 / 10:23≈ on time ≈ on time
10:29≈ on time ≈ +1 min
10:35≈ on time ≈ +1 min
10:39 / 10:47≈ on time ≈ +1 min
10:52≈ on time ≈ +1 min
10:56≈ on time ≈ +1 min
11:03≈ on time ≈ +2 min
11:10on 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
Wed 4 NovMaarheeze 11:23Partial coverage+5 min+5 min
Tue 3 NovMaarheeze 11:19Partial coverage0 min—
Mon 2 NovMaarheeze 11:17No data—
Sat 31 OctMaarheeze 11:19+1 min—
Fri 30 OctMaarheeze 11:21No data—
Thu 29 OctMaarheeze 11:18Partial coverage0 min—
Wed 28 OctMaarheeze 11:18Partial coverage0 min—
Tue 27 OctMaarheeze 11:17No data—
Mon 26 OctMaarheeze 11:18No data—
Sun 25 OctEindhoven Strijp-S 10:50No data—
Sat 24 OctMaarheeze 11:18Partial coverage0 min—
Fri 23 OctMaarheeze 11:18No data—
Thu 22 OctMaarheeze 11:23No data—
Wed 21 OctMaarheeze 11:18Partial coverage0 min—
Tue 20 OctMaarheeze 11:18Partial coverage0 min—
Mon 19 OctMaarheeze 11:17Partial coverage0 min—
Sun 18 OctEindhoven Strijp-S 10:490 min—
Sat 17 OctMaarheeze 11:180 min—
Fri 16 OctMaarheeze 11:18No data—
Thu 15 OctMaarheeze 11:18No data—
Wed 14 OctMaarheeze 11:17No data—
Tue 13 OctMaarheeze 11:18No data—
Mon 12 OctMaarheeze 11:21Partial coverage0 min—
Sun 11 OctEindhoven Strijp-S 10:500 min—
Sat 10 OctMaarheeze 11:180 min+1 min
Fri 9 OctMaarheeze 11:20+3 min+3 min
Thu 8 OctMaarheeze 11:18No data—
Wed 7 OctBest 12:01Partial coverage0 min—
Tue 6 OctMaarheeze 11:21Partial coverage+3 min+4 min
Mon 5 OctMaarheeze 11:18No data—