Train NS 6459 Tilburg Universiteit – Weert

Tilburg Universiteit 17:04 → Weert 18:10 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:04 from Tilburg Universiteit · Fri 6 Nov

Next departure 17:04 today · Tilburg Universiteit
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 7 full · 7 partial · 14 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 7 full · 10 partial · 68 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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 7 Oct Max en route +5 min · last fix heading to Maarheeze +4 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=3
  • 100% T n=1
  • 67% W n=3
  • 100% T n=1
  • 100% F n=4
  • 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, 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
17:04on time on time
17:08 / 17:09≈ on time ≈ on time
17:15≈ on time ≈ on time
17:22 / 17:23≈ on time ≈ on time
17:29≈ on time ≈ on time
17:35≈ on time ≈ on time
17:39 / 17:47≈ on time ≈ +1 min
17:52≈ on time ≈ +1 min
17:56≈ on time ≈ +1 min
18:03≈ on time ≈ +1 min
18:10on 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
Thu 5 NovMaarheeze 18:17No data—
Wed 4 NovMaarheeze 18:17Partial coverage0 min—
Tue 3 NovMaarheeze 18:22No data—
Mon 2 NovMaarheeze 18:17No data—
Sat 31 OctMaarheeze 18:19+1 min—
Fri 30 OctMaarheeze 18:170 min—
Thu 29 OctHeeze 18:12No data—
Wed 28 OctMaarheeze 18:17No data—
Tue 27 OctMaarheeze 18:18No data—
Mon 26 OctMaarheeze 18:17Partial coverage0 min—
Sun 25 OctEindhoven Strijp-S 17:50No data—
Sat 24 OctMaarheeze 18:18Partial coverage0 min—
Fri 23 OctMaarheeze 18:18Partial coverage0 min—
Thu 22 OctMaarheeze 18:12No data—
Wed 21 OctMaarheeze 18:17Partial coverage0 min—
Tue 20 OctMaarheeze 18:18No data—
Mon 19 OctMaarheeze 18:17No data—
Sun 18 OctEindhoven Strijp-S 17:500 min—
Sat 17 OctMaarheeze 18:19No data—
Fri 16 OctMaarheeze 18:190 min—
Thu 15 OctMaarheeze 18:17No data—
Wed 14 OctMaarheeze 18:26No data—
Tue 13 OctMaarheeze 18:17No data—
Mon 12 OctMaarheeze 18:17Partial coverage0 min—
Sun 11 OctEindhoven Strijp-S 17:500 min—
Sat 10 OctMaarheeze 18:18+1 min—
Fri 9 OctMaarheeze 18:17+1 min—
Thu 8 OctMaarheeze 18:17Partial coverage+1 min+1 min
Wed 7 OctMaarheeze 18:20Partial coverage+4 min+5 min
Tue 6 OctMaarheeze 18:17Partial coverage0 min—