Train NS 6434 Weert – Tilburg Universiteit

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

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 09:20 from Weert · Sat 7 Nov

Next departure 09:20 today · Weert
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 6 full · 7 partial · 15 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 6 full · 10 partial · 69 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=1
  • 100% T n=2
  • 100% W n=3
  • 100% T n=3
  • 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
09:20on time on time
09:26≈ on time ≈ on time
09:33≈ on time ≈ on time
09:37≈ on time ≈ on time
09:43 / 09:51≈ on time ≈ on time
09:54≈ on time ≈ on time
10:00≈ on time ≈ on time
10:07≈ on time ≈ on time
10:14≈ on time ≈ on time
10:20 / 10:24≈ on time ≈ on time
10: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
Fri 6 NovTilburg 10:39No data—
Thu 5 NovTilburg 10:43No data—
Wed 4 NovTilburg 10:39Partial coverage0 min—
Tue 3 NovTilburg 10:40No data—
Mon 2 NovTilburg 10:39No data—
Sat 31 OctGeldrop 09:510 min—
Fri 30 OctTilburg 10:39No data—
Thu 29 OctTilburg 10:39Partial coverage0 min—
Wed 28 OctTilburg 10:39No data—
Tue 27 OctTilburg 10:39No data—
Mon 26 OctTilburg 10:38No data—
Sun 25 OctTilburg 10:41No data—
Sat 24 OctTilburg 10:39Partial coverage0 min—
Fri 23 OctTilburg 10:39No data—
Thu 22 OctTilburg 10:38Partial coverage0 min—
Wed 21 OctTilburg 10:39Partial coverage0 min—
Tue 20 OctTilburg 10:39Partial coverage0 min—
Mon 19 OctTilburg 10:38Partial coverage0 min—
Sun 18 OctTilburg 10:380 min—
Sat 17 OctTilburg 10:390 min—
Fri 16 OctTilburg 10:39No data—
Thu 15 OctMaarheeze 10:58No data—
Wed 14 OctTilburg 10:39No data—
Tue 13 OctTilburg 10:39No data—
Mon 12 OctTilburg 10:40No data—
Sun 11 OctTilburg 10:390 min—
Sat 10 OctTilburg 10:390 min—
Fri 9 OctTilburg 10:39+1 min—
Thu 8 OctTilburg 10:38Partial coverage0 min—
Wed 7 OctTilburg 10:40Partial coverage0 min—