Train NS 6485 Tilburg Universiteit – Weert

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

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 23:34 from Tilburg Universiteit · Sat 7 Nov

Next departure 23:34 today · Tilburg Universiteit
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 18 full · 1 partial · 7 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 21 full · 2 partial · 20 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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 23 Oct Max en route +4 min · last fix heading to — +4 min
  • Fri 16 Oct Max en route +5 min · last fix heading to — +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 91% · 21
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
23:34on time on time
23:38 / 23:39≈ on time ≈ on time
23:45≈ on time ≈ on time
23:52 / 23:53≈ on time ≈ +1 min
23:59≈ on time ≈ +1 min
00:05≈ on time ≈ +1 min
00:09 / 00:17≈ on time ≈ +1 min
00:22≈ on time ≈ +1 min
00:26≈ on time ≈ +1 min
00:33≈ on time ≈ +2 min
00:40on time +2 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
Fri 6 Nov— 00:39+1 min—
Thu 5 Nov— 00:39No data—
Wed 4 Nov— 00:42+1 min+1 min
Tue 3 Nov— 00:480 min—
Sun 1 Nov— 00:490 min—
Fri 30 Oct— 23:48No data—
Wed 28 Oct— 00:410 min—
Tue 27 Oct— 00:570 min—
Mon 26 Oct— 00:500 min—
Sun 25 OctMaarheeze 00:49No data—
Sat 24 Oct— 00:41No data—
Fri 23 Oct— 00:46+4 min+4 min
Thu 22 Oct— 01:14No data—
Wed 21 Oct— 00:420 min—
Tue 20 Oct— 00:420 min—
Mon 19 Oct— 00:430 min—
Sun 18 OctMaarheeze 00:530 min—
Sat 17 OctTilburg Universiteit 00:44No data—
Fri 16 Oct— 00:48+4 min+5 min
Thu 15 Oct— 00:41No data—
Wed 14 Oct— 00:430 min—
Tue 13 Oct— 00:420 min—
Mon 12 Oct— 00:430 min—
Sun 11 OctMaarheeze 00:47Partial coverage0 min—
Sat 10 Oct— 00:42+2 min+2 min
Fri 9 Oct— 00:41+1 min—
Thu 8 Oct— 00:430 min—
Wed 7 Oct— 00:410 min—
Tue 6 Oct— 00:420 min—
Mon 5 OctEindhoven Centraal 00:43Partial coverage0 min—