Train NS 6424 Weert – Tilburg Universiteit

Weert 06:50 → Tilburg Universiteit 07:59 Mon, Tue, Wed, Thu, Fri, Sat 1 h 09 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

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

  1. Weert06:50
  2. Heeze07:03
  3. Geldrop07:07
  4. Eindhoven Strijp-S07:24
  5. Boxtel07:37
  6. Tilburg07:50
  7. Tilburg Universiteit07:59

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

Next departure 06:50 tomorrow · Weert
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 3 full · 21 partial · 2 no data
On-time · 90 days
96%
24/25 runs under 3 min
RT coverage: 3 full · 22 partial · 53 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: +1 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

  • Thu 8 Oct Max en route +5 min · last fix heading to Tilburg +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 24
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=5
  • 75% T n=4
  • 100% F n=4
  • 100% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 25 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
06:50on time on time
06:56— —
07:03— —
07:07— —
07:13 / 07:21— —
07:24— —
07:30— —
07:37— —
07:44— —
07:50 / 07:54— —
07: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 08:12No data—
Wed 4 NovTilburg 08:09Partial coverage+1 min+1 min
Tue 3 NovTilburg 08:09Partial coverage0 min—
Mon 2 NovTilburg 08:09No data—
Sat 31 OctGeldrop 07:220 min—
Fri 30 OctTilburg 08:09Partial coverage0 min—
Thu 29 OctTilburg 08:09Partial coverage0 min—
Wed 28 OctTilburg 08:080 min—
Tue 27 OctTilburg 08:08Partial coverage0 min—
Mon 26 OctTilburg 08:08Partial coverage0 min—
Sat 24 OctTilburg 08:08Partial coverage0 min—
Fri 23 OctTilburg 08:09Partial coverage0 min—
Thu 22 OctTilburg 08:13Partial coverage0 min—
Wed 21 OctTilburg 08:11Partial coverage0 min—
Tue 20 OctTilburg 08:09Partial coverage0 min—
Mon 19 OctTilburg 08:09Partial coverage0 min—
Sat 17 OctTilburg 08:09Partial coverage0 min—
Fri 16 OctTilburg 08:08Partial coverage0 min—
Thu 15 OctTilburg 08:10Partial coverage0 min—
Wed 14 OctTilburg 08:10Partial coverage0 min—
Tue 13 OctTilburg 08:10Partial coverage0 min—
Mon 12 OctTilburg 08:09Partial coverage0 min—
Sat 10 OctTilburg 08:09Partial coverage0 min+2 min
Fri 9 OctTilburg 08:09Partial coverage0 min—
Thu 8 OctTilburg 08:17+5 min+5 min
Wed 7 OctTilburg 08:10Partial coverage+1 min+2 min
Tue 6 OctTilburg 08:11Partial coverage+2 min+3 min
Mon 5 OctTilburg 08:10No data—
Sat 3 OctTilburg 08:08No data—
Fri 2 OctTilburg 08:10No data—