Train NS 6450 Weert – Tilburg Universiteit

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

✓ Today’s run finished

Today, last fix heading to Tilburg at 14:39 +1 min

  1. Weert13:20
  2. Heeze13:33
  3. Geldrop13:37
  4. Eindhoven Strijp-S13:54
  5. Boxtel14:07
  6. Tilburg14:20
  7. Tilburg Universiteit14:29

Next service: tomorrow 13:20 from Weert · Tue 10 Nov

Next departure 13:20 tomorrow · Weert
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 6 full · 9 partial · 14 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 8 full · 13 partial · 65 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

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

  • Early 0% · 0
  • On time 100% · 21
  • 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=1
  • 100% W n=5
  • 100% T n=2
  • 100% F n=3
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

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