Train NS 6470 Weert – Tilburg Universiteit

Weert 18:20 → Tilburg Universiteit 19:29 Daily 1 h 09 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 18:20 from Weert · Thu 5 Nov

Next departure 18:20 today · Weert
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 10 full · 3 partial · 14 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 12 full · 3 partial · 51 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 Tilburg Universiteit, 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 9 Oct Max en route +7 min · last fix heading to Heeze +6 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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
18:20on time on time
18:26≈ on time ≈ +1 min
18:33≈ on time ≈ +1 min
18:37≈ on time ≈ +1 min
18:43 / 18:51≈ on time ≈ +1 min
18:54≈ on time ≈ +1 min
19:00≈ on time ≈ +1 min
19:07≈ on time ≈ +1 min
19:14≈ on time ≈ +1 min
19:20 / 19:24≈ on time ≈ +2 min
19:29on 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
Wed 4 Nov— 19:34No data—
Tue 3 Nov— 19:29No data—
Mon 2 Nov— 19:290 min—
Sat 31 OctGeldrop 18:520 min—
Fri 30 OctEindhoven Strijp-S 19:30No data—
Wed 28 Oct— 19:300 min—
Tue 27 Oct— 19:31No data—
Mon 26 Oct— 19:31No data—
Sun 25 OctTilburg 19:38No data—
Sat 24 OctTilburg 19:45No data—
Fri 23 OctTilburg 19:38Partial coverage+2 min+3 min
Thu 22 OctGeldrop 19:31No data—
Wed 21 OctGeldrop 19:31Partial coverage0 min—
Tue 20 OctGeldrop 19:31No data—
Mon 19 OctGeldrop 19:30No data—
Sun 18 OctTilburg 19:380 min—
Sat 17 OctTilburg 19:40No data—
Fri 16 OctTilburg 19:380 min—
Thu 15 OctMaarheeze 19:31No data—
Wed 14 OctTilburg 19:38No data—
Tue 13 OctGeldrop 19:31No data—
Mon 12 OctGeldrop 19:31Partial coverage0 min—
Sun 11 OctTilburg 19:390 min—
Sat 10 OctTilburg 19:390 min—
Fri 9 OctHeeze 19:37+6 min+7 min
Thu 8 Oct— 19:290 min—
Wed 7 Oct— 19:300 min—
Tue 6 Oct— 19:310 min—
Mon 5 Oct— 19:31+2 min+3 min
Sun 4 OctTilburg 19:38No data—