Train NS 6454 Weert – Tilburg Universiteit

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

✓ Today’s run finished

Today, last fix heading to Tilburg at 15:38 0 min

  1. Weert14:20
  2. Heeze14:34
  3. Geldrop14:38
  4. Eindhoven Strijp-S14:54
  5. Boxtel15:07
  6. Tilburg15:20
  7. Tilburg Universiteit15:29

Next service: tomorrow 14:20 from Weert · Sun 8 Nov

Next departure 14:20 tomorrow · Weert
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 11 full · 1 partial · 17 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 15 full · 1 partial · 70 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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 100% · 16
  • 3–10 min 0% · 0
  • 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
  • 100% 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
14:20on time on time
14:26≈ on time ≈ on time
14:34≈ on time ≈ on time
14:38≈ on time ≈ on time
14:44 / 14:51≈ on time ≈ on time
14:54≈ on time ≈ on time
15:00≈ on time ≈ on time
15:07≈ on time ≈ on time
15:14≈ on time ≈ on time
15:20 / 15:24≈ on time ≈ on time
15:29on time on time

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 15:38Partial coverage0 min—
Fri 6 NovTilburg 15:39No data—
Thu 5 NovTilburg 15:40No data—
Wed 4 NovTilburg 15:380 min—
Tue 3 NovTilburg 15:39No data—
Mon 2 NovTilburg 15:38No data—
Sat 31 OctGeldrop 14:520 min—
Fri 30 OctTilburg 15:38No data—
Thu 29 OctTilburg 15:390 min—
Wed 28 OctTilburg 15:38No data—
Tue 27 OctTilburg 15:39No data—
Mon 26 OctTilburg 15:38No data—
Sun 25 OctTilburg 15:38No data—
Sat 24 OctTilburg 15:380 min—
Fri 23 OctTilburg 15:38No data—
Thu 22 OctTilburg 15:39No data—
Wed 21 OctTilburg 15:39No data—
Tue 20 OctTilburg 15:390 min—
Mon 19 OctTilburg 15:410 min—
Sun 18 OctTilburg 15:380 min—
Sat 17 OctTilburg 15:38No data—
Fri 16 OctTilburg 15:38No data—
Thu 15 OctTilburg 15:39No data—
Wed 14 OctTilburg 15:43No data—
Tue 13 OctTilburg 15:38No data—
Mon 12 OctTilburg 15:380 min—
Sun 11 OctTilburg 15:380 min—
Sat 10 OctTilburg 15:39+1 min+2 min
Fri 9 OctTilburg 15:380 min—
Thu 8 OctTilburg 15:380 min—