Train NS 6463 Tilburg Universiteit – Weert

Tilburg Universiteit 18:04 → Weert 19:10 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:04 from Tilburg Universiteit · Thu 5 Nov

Next departure 18:04 today · Tilburg Universiteit
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 8 full · 9 partial · 11 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 8 full · 11 partial · 63 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 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 9 Oct Max en route +32 min · last fix heading to Eindhoven Strijp-S +31 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 5% · 1

On-time by weekday

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

Stops and timetable

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

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