Train NS 6441 Tilburg Universiteit – Weert

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

✓ Today’s run finished

Today, last fix heading to Maarheeze at 13:48 No data

  1. Tilburg Universiteit12:34
  2. Oisterwijk12:45
  3. Boxtel12:52
  4. Eindhoven Strijp-S13:05
  5. Geldrop13:22
  6. Maarheeze13:33
  7. Weert13:40

Next service: tomorrow 12:34 from Tilburg Universiteit · Fri 6 Nov

Next departure 12:34 tomorrow · Tilburg Universiteit
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 1 full · 14 partial · 15 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 1 full · 16 partial · 72 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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 +12 min · last fix heading to Maarheeze +12 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Maarheeze +3 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 88% · 15
  • 3–10 min 6% · 1
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 50% T n=2
  • 100% W n=4
  • 100% T n=2
  • 0% F n=1
  • 100% 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, 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
12:34on time on time
12:38 / 12:39— —
12:45— —
12:52 / 12:53— —
12:59— —
13:05— —
13:09 / 13:17— —
13:22— —
13:26— —
13:33— —
13: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
Thu 5 NovMaarheeze 13:48No data—
Wed 4 NovMaarheeze 13:48Partial coverage+1 min—
Tue 3 NovMaarheeze 13:48No data—
Mon 2 NovMaarheeze 13:48Partial coverage0 min—
Sun 1 NovMaarheeze 13:52+2 min+3 min
Sat 31 OctMaarheeze 13:49No data—
Fri 30 OctMaarheeze 13:47No data—
Thu 29 OctMaarheeze 13:48Partial coverage0 min—
Wed 28 OctMaarheeze 13:48Partial coverage0 min—
Tue 27 OctMaarheeze 13:47No data—
Mon 26 OctMaarheeze 13:48No data—
Sun 25 OctMaarheeze 13:48No data—
Sat 24 OctMaarheeze 13:49Partial coverage+1 min+2 min
Fri 23 OctMaarheeze 13:48No data—
Thu 22 OctMaarheeze 13:48No data—
Wed 21 OctMaarheeze 13:49Partial coverage0 min—
Tue 20 OctMaarheeze 13:48Partial coverage0 min—
Mon 19 OctMaarheeze 13:47No data—
Sun 18 OctMaarheeze 13:48Partial coverage+1 min—
Sat 17 OctMaarheeze 13:48No data—
Fri 16 OctMaarheeze 13:48No data—
Thu 15 OctMaarheeze 13:48No data—
Wed 14 OctMaarheeze 13:47No data—
Tue 13 OctMaarheeze 13:48No data—
Mon 12 OctMaarheeze 13:49Partial coverage0 min—
Sun 11 OctMaarheeze 13:48Partial coverage0 min+1 min
Sat 10 OctMaarheeze 13:48Partial coverage+1 min—
Fri 9 OctMaarheeze 13:59Partial coverage+12 min+12 min
Thu 8 OctMaarheeze 13:48Partial coverage0 min+1 min
Wed 7 OctMaarheeze 13:48Partial coverage+1 min—