Train NS 6469 Tilburg Universiteit – Weert

Tilburg Universiteit 19:34 → Weert 20: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 19:34 from Tilburg Universiteit · Fri 6 Nov

Next departure 19:34 today · Tilburg Universiteit
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 8 full · 5 partial · 14 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 11 full · 5 partial · 38 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

  • Sun 11 Oct Max en route +4 min · last fix heading to Maarheeze +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 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=1
  • 100% W n=3
  • 100% T n=1
  • 100% F n=3
  • 100% S n=3
  • 67% S n=3

Stops and timetable

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

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