Train NS 6455 Tilburg Universiteit – Weert

Tilburg Universiteit 16:03 → Weert 17:10 Daily 1 h 07 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Maarheeze at 17:18 0 min

  1. Tilburg Universiteit16:03
  2. Oisterwijk16:15
  3. Boxtel16:21
  4. Eindhoven Strijp-S16:35
  5. Geldrop16:52
  6. Maarheeze17:03
  7. Weert17:10

Next service: tomorrow 16:03 from Tilburg Universiteit · Sun 8 Nov

Next departure 16:03 tomorrow · Tilburg Universiteit
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 14 full · 1 partial · 14 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 18 full · 1 partial · 67 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

  • Fri 6 Nov Max en route +4 min · last fix heading to Maarheeze +3 min

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 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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