Train NS 6415 Tilburg Universiteit – Weert

Tilburg Universiteit 06:04 → Weert 07:10 Mon, Tue, Wed, Thu, Fri 1 h 06 min · 11 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 06:04 from Tilburg Universiteit · Mon 9 Nov

Next departure 06:04 Monday · Tilburg Universiteit
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 3 full · 17 partial · 1 no data
On-time · 90 days
87%
20/23 runs under 3 min
RT coverage: 3 full · 20 partial · 41 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Thu 15 Oct Max en route +14 min · last fix heading to Maarheeze +14 min
  • Thu 22 Oct Max en route +5 min · last fix heading to Maarheeze +5 min
  • Thu 29 Oct Max en route +5 min · last fix heading to Maarheeze +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 20
  • 3–10 min 9% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=5
  • 40% T n=5
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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
06:04on time on time
06:08 / 06:09— —
06:15— —
06:22 / 06:23— —
06:29— —
06:35— —
06:39 / 06:47— —
06:52— —
06:56— —
07:03— —
07:10— —

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
Fri 6 NovMaarheeze 07:18No data—
Thu 5 NovMaarheeze 07:24Partial coverage0 min—
Wed 4 NovMaarheeze 07:18Partial coverage0 min+1 min
Tue 3 NovMaarheeze 07:19Partial coverage+2 min+2 min
Mon 2 NovMaarheeze 07:19Partial coverage0 min—
Fri 30 OctMaarheeze 07:20+3 min+3 min
Thu 29 OctMaarheeze 07:22Partial coverage+4 min+5 min
Wed 28 OctMaarheeze 07:19Partial coverage+2 min+2 min
Tue 27 OctMaarheeze 07:20Partial coverage+2 min+3 min
Mon 26 OctMaarheeze 07:18Partial coverage+1 min+1 min
Fri 23 OctMaarheeze 07:20Partial coverage+2 min+3 min
Thu 22 OctMaarheeze 07:22Partial coverage+5 min+5 min
Wed 21 OctMaarheeze 07:18Partial coverage+1 min—
Tue 20 OctMaarheeze 07:18Partial coverage+1 min+1 min
Mon 19 OctMaarheeze 07:18Partial coverage+1 min+1 min
Fri 16 OctMaarheeze 07:19+1 min+2 min
Thu 15 OctMaarheeze 07:34Partial coverage+14 min+14 min
Wed 14 OctMaarheeze 07:18Partial coverage+1 min—
Tue 13 OctMaarheeze 07:18Partial coverage+1 min—
Mon 12 OctMaarheeze 07:19Partial coverage+2 min+2 min
Fri 9 OctMaarheeze 07:18+1 min+1 min
Thu 8 OctMaarheeze 07:18Partial coverage+1 min—
Wed 7 OctMaarheeze 07:19Partial coverage0 min+2 min
Tue 6 OctMaarheeze 07:25Partial coverage0 min+7 min
Mon 5 OctMaarheeze 07:19No data—
Fri 2 OctMaarheeze 07:18No data—
Thu 1 OctMaarheeze 07:19No data—
Wed 30 SeptMaarheeze 07:21No data—
Tue 29 SeptMaarheeze 07:24No data—
Mon 28 SeptMaarheeze 07:18No data—