Train NS 6437 Tilburg Universiteit – Weert

Tilburg Universiteit 11:34 → Weert 12: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 11:34 from Tilburg Universiteit · Thu 5 Nov

Next departure 11:34 today · Tilburg Universiteit
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 1 full · 11 partial · 17 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 1 full · 13 partial · 74 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

  • Sun 18 Oct Max en route +6 min · last fix heading to Maarheeze +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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