Train NS 6452 Weert – Tilburg Universiteit

Weert 13:50 → Tilburg Universiteit 14:59 Daily 1 h 09 min · 11 stops NS (Nederlandse Spoorwegen)

Running now · updated 14:26

Heading to Tilburg Universiteit 0 min

Estimated arrival at Tilburg Universiteit 14:59

  1. Weert13:50
  2. Heeze14:03
  3. Geldrop14:07
  4. Eindhoven Strijp-S14:24
  5. Boxtel14:37
  6. Oisterwijk14:44
  7. Tilburg Universiteit14:59

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 13 runs arrived on time.

On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 3 full · 10 partial · 17 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 4 full · 15 partial · 70 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 Tilburg Universiteit, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

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 100% · 19
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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 10Today
13:50on time on time
13:56— —
14:03— —
14:07— —
14:13 / 14:21— —
14:24— —
14:30— —
14:37— —
14:44— —
14:50 / 14:54— —
14:59— —

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
Mon 9 NovEindhoven Strijp-S 14:24Partial coverage0 min—
Sun 8 NovTilburg 15:12+3 min+5 min
Sat 7 NovTilburg 15:080 min—
Fri 6 NovTilburg 15:08No data—
Thu 5 NovTilburg 15:09No data—
Wed 4 NovTilburg 15:09Partial coverage0 min—
Tue 3 NovTilburg 15:08No data—
Mon 2 NovTilburg 15:08Partial coverage0 min—
Sun 1 NovGeldrop 14:220 min—
Sat 31 OctGeldrop 14:21No data—
Fri 30 OctTilburg 15:09No data—
Thu 29 OctTilburg 15:08Partial coverage0 min—
Wed 28 OctTilburg 15:08Partial coverage0 min—
Tue 27 OctTilburg 15:09No data—
Mon 26 OctTilburg 15:08No data—
Sun 25 OctTilburg 15:13No data—
Sat 24 OctTilburg 15:10Partial coverage+1 min+3 min
Fri 23 OctTilburg 15:11No data—
Thu 22 OctTilburg 15:08No data—
Wed 21 OctTilburg 15:10Partial coverage0 min—
Tue 20 OctTilburg 15:08No data—
Mon 19 OctTilburg 15:09No data—
Sun 18 OctTilburg 15:10Partial coverage+1 min+2 min
Sat 17 OctTilburg 15:08No data—
Fri 16 OctTilburg 15:08No data—
Thu 15 OctTilburg 15:08No data—
Wed 14 OctTilburg 15:09No data—
Tue 13 OctTilburg 15:08No data—
Mon 12 OctTilburg 15:09Partial coverage0 min—
Sun 11 OctTilburg 15:35Partial coverage0 min+26 min