Train NS 6435 Tilburg Universiteit – Weert

Tilburg Universiteit 11:04 → Weert 12:10 Daily 1 h 06 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 9 November +4 min

Next service: today 11:04 from Tilburg Universiteit · Tue 10 Nov

Next departure 11:04 today · Tilburg Universiteit
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 6 full · 10 partial · 12 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 9 full · 13 partial · 63 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 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

  • Mon 9 Nov Max en route +4 min · last fix heading to Maarheeze +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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:04on time on time
11:08 / 11:09≈ on time ≈ on time
11:15≈ on time ≈ on time
11:22 / 11:23≈ on time ≈ on time
11:29≈ on time ≈ on time
11:35≈ on time ≈ on time
11:39 / 11:47≈ on time ≈ on time
11:52≈ on time ≈ +1 min
11:56≈ on time ≈ +1 min
12:03≈ on time ≈ +1 min
12:10on time +1 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
Mon 9 NovMaarheeze 12:19Partial coverage+4 min+4 min
Sun 8 NovEindhoven Strijp-S 11:490 min—
Sat 7 NovMaarheeze 12:170 min—
Fri 6 NovMaarheeze 12:19No data—
Thu 5 NovMaarheeze 12:18No data—
Wed 4 NovMaarheeze 12:18Partial coverage+1 min—
Tue 3 NovMaarheeze 12:18Partial coverage0 min—
Mon 2 NovMaarheeze 12:19No data—
Sat 31 OctMaarheeze 12:19+1 min—
Fri 30 OctMaarheeze 12:17No data—
Thu 29 OctMaarheeze 12:18Partial coverage0 min—
Wed 28 OctMaarheeze 12:18Partial coverage0 min—
Tue 27 OctEindhoven Strijp-S 11:50No data—
Mon 26 OctMaarheeze 12:21No data—
Sun 25 OctEindhoven Strijp-S 11:50No data—
Sat 24 OctMaarheeze 12:18Partial coverage0 min—
Fri 23 OctMaarheeze 12:18No data—
Thu 22 OctHeeze 12:44Partial coverage0 min—
Wed 21 OctMaarheeze 12:22Partial coverage0 min—
Tue 20 OctMaarheeze 12:22Partial coverage0 min—
Mon 19 OctMaarheeze 12:17Partial coverage0 min—
Sun 18 OctEindhoven Strijp-S 11:500 min—
Sat 17 OctMaarheeze 12:180 min—
Fri 16 OctMaarheeze 12:180 min—
Thu 15 OctMaarheeze 12:21No data—
Wed 14 OctMaarheeze 12:18No data—
Tue 13 OctMaarheeze 12:18No data—
Mon 12 OctMaarheeze 12:17No data—
Sun 11 OctEindhoven Strijp-S 11:490 min—
Sat 10 OctMaarheeze 12:170 min—