Train NS 6468 Weert – Tilburg Universiteit

Weert 17:50 → Tilburg Universiteit 18:59 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 17:50 from Weert · Thu 5 Nov

Next departure 17:50 today · Weert
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 1 full · 16 partial · 12 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 1 full · 18 partial · 69 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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

  • Tue 6 Oct Max en route +6 min · last fix heading to Heeze +6 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Best +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 67% T n=3
  • 100% W n=2
  • 100% T n=3
  • 50% 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, 19 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
17:50on time on time
17:56— —
18:03— —
18:07— —
18:13 / 18:21— —
18:24— —
18:30— —
18:37— —
18:44— —
18:50 / 18:54— —
18: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
Wed 4 NovGeldrop 18:59No data—
Tue 3 NovGeldrop 18:59Partial coverage0 min—
Mon 2 NovGeldrop 18:59Partial coverage0 min—
Sun 1 NovGeldrop 18:22+1 min—
Sat 31 OctGeldrop 18:21No data—
Fri 30 OctTilburg 19:08No data—
Thu 29 OctMaarheeze 19:01Partial coverage0 min—
Wed 28 OctGeldrop 19:00Partial coverage0 min—
Tue 27 OctHeeze 19:01No data—
Mon 26 OctGeldrop 19:01Partial coverage0 min—
Sun 25 OctTilburg 19:09No data—
Sat 24 OctTilburg 19:09Partial coverage0 min—
Fri 23 OctTilburg 19:08Partial coverage+2 min+3 min
Thu 22 OctOisterwijk 19:02Partial coverage0 min—
Wed 21 OctBoxtel 19:02No data—
Tue 20 OctOisterwijk 19:02Partial coverage0 min—
Mon 19 OctBoxtel 19:02No data—
Sun 18 OctTilburg 19:09Partial coverage+1 min—
Sat 17 OctTilburg 19:10No data—
Fri 16 OctTilburg 19:08No data—
Thu 15 OctBest 19:02No data—
Wed 14 OctTilburg 19:08No data—
Tue 13 OctBoxtel 19:00No data—
Mon 12 OctOisterwijk 19:01Partial coverage0 min—
Sun 11 OctTilburg 19:09Partial coverage+1 min—
Sat 10 OctTilburg 19:11Partial coverage+2 min+3 min
Fri 9 OctBest 19:03Partial coverage+4 min+4 min
Thu 8 OctHeeze 19:00Partial coverage0 min—
Wed 7 OctGeldrop 19:00Partial coverage0 min—
Tue 6 OctHeeze 18:44Partial coverage+6 min+6 min