Train NS 6445 Tilburg Universiteit – Weert

Tilburg Universiteit 13:34 → Weert 14:40 Daily 1 h 06 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 13:34 from Tilburg Universiteit · Thu 5 Nov

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

  • Sat 24 Oct Max en route +5 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=1
  • 100% T n=2
  • 100% W n=4
  • 100% T n=2
  • 100% F n=2
  • 50% S n=2
  • 100% 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
13:34on time on time
13:38 / 13:39— —
13:45— —
13:52 / 13:53— —
13:59— —
14:05— —
14:09 / 14:17— —
14:22— —
14:26— —
14:33— —
14:40— —

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 14:48Partial coverage+1 min—
Tue 3 NovMaarheeze 14:49No data—
Mon 2 NovMaarheeze 14:48No data—
Sun 1 NovMaarheeze 14:50+1 min—
Sat 31 OctMaarheeze 14:49No data—
Fri 30 OctMaarheeze 14:48No data—
Thu 29 OctMaarheeze 14:48No data—
Wed 28 OctMaarheeze 14:48Partial coverage0 min—
Tue 27 OctMaarheeze 14:48No data—
Mon 26 OctMaarheeze 14:48No data—
Sun 25 OctMaarheeze 14:48No data—
Sat 24 OctMaarheeze 14:53Partial coverage+4 min+5 min
Fri 23 OctMaarheeze 14:51No data—
Thu 22 OctMaarheeze 14:49Partial coverage0 min—
Wed 21 OctMaarheeze 14:47Partial coverage0 min—
Tue 20 OctMaarheeze 14:50Partial coverage0 min—
Mon 19 OctMaarheeze 14:48No data—
Sun 18 OctMaarheeze 14:48Partial coverage+1 min—
Sat 17 OctMaarheeze 14:48No data—
Fri 16 OctMaarheeze 14:490 min—
Thu 15 OctMaarheeze 14:47No data—
Wed 14 OctMaarheeze 14:49No data—
Tue 13 OctMaarheeze 14:48No data—
Mon 12 OctMaarheeze 14:48No data—
Sun 11 OctMaarheeze 14:48Partial coverage+1 min—
Sat 10 OctMaarheeze 14:48Partial coverage+1 min—
Fri 9 OctMaarheeze 14:49Partial coverage+1 min+2 min
Thu 8 OctMaarheeze 14:48Partial coverage+1 min—
Wed 7 OctMaarheeze 14:48Partial coverage+1 min—
Tue 6 OctMaarheeze 14:48Partial coverage+1 min—