Train NS 6458 Weert – Tilburg Universiteit

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 15:20 from Weert · Sun 8 Nov

Next departure 15:20 today · Weert
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 10 full · 1 partial · 17 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 15 full · 1 partial · 69 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

  • Sun 18 Oct Max en route +7 min · last fix heading to Tilburg +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 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=2
  • 100% T n=2
  • 100% F n=1
  • 100% S n=4
  • 50% S n=2

Stops and timetable

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

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