Train NS 6460 Weert – Tilburg Universiteit

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

✓ Today’s run finished

Today, last fix heading to Tilburg at 17:08 No data

  1. Weert15:50
  2. Heeze16:03
  3. Geldrop16:07
  4. Eindhoven Strijp-S16:24
  5. Boxtel16:37
  6. Tilburg16:50
  7. Tilburg Universiteit16:59

Next service: tomorrow 15:50 from Weert · Fri 6 Nov

Next departure 15:50 tomorrow · Weert
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 2 full · 13 partial · 15 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 2 full · 15 partial · 72 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

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

  • Early 0% · 0
  • On time 100% · 17
  • 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=1
  • 100% F n=2
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 17 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:50on time on time
15:56— —
16:03— —
16:07— —
16:13 / 16:21— —
16:24— —
16:30— —
16:37— —
16:44— —
16:50 / 16:54— —
16:59— —

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
Thu 5 NovTilburg 17:08No data—
Wed 4 NovTilburg 17:08Partial coverage0 min—
Tue 3 NovTilburg 17:08No data—
Mon 2 NovTilburg 17:08No data—
Sun 1 NovGeldrop 16:220 min—
Sat 31 OctGeldrop 16:21No data—
Fri 30 OctTilburg 17:11No data—
Thu 29 OctTilburg 17:08No data—
Wed 28 OctTilburg 17:08Partial coverage0 min—
Tue 27 OctTilburg 17:08No data—
Mon 26 OctTilburg 17:080 min—
Sun 25 OctTilburg 17:08No data—
Sat 24 OctTilburg 17:08Partial coverage+1 min—
Fri 23 OctTilburg 17:13Partial coverage0 min—
Thu 22 OctTilburg 17:09No data—
Wed 21 OctTilburg 17:09Partial coverage0 min—
Tue 20 OctTilburg 17:08No data—
Mon 19 OctTilburg 17:08No data—
Sun 18 OctTilburg 17:08Partial coverage0 min—
Sat 17 OctTilburg 17:09No data—
Fri 16 OctTilburg 17:09No data—
Thu 15 OctTilburg 17:11No data—
Wed 14 OctTilburg 17:08Partial coverage0 min—
Tue 13 OctTilburg 17:09No data—
Mon 12 OctTilburg 17:08Partial coverage0 min—
Sun 11 OctTilburg 17:08Partial coverage0 min—
Sat 10 OctTilburg 17:08Partial coverage0 min—
Fri 9 OctTilburg 17:08Partial coverage0 min—
Thu 8 OctTilburg 17:08Partial coverage+2 min+2 min
Wed 7 OctTilburg 17:08Partial coverage0 min—