Train NS 6428 Weert – Tilburg Universiteit

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

✓ Today’s run finished

Today, last fix heading to Tilburg at 09:08 0 min

  1. Weert07:50
  2. Heeze08:03
  3. Geldrop08:07
  4. Eindhoven Strijp-S08:24
  5. Boxtel08:37
  6. Tilburg08:50
  7. Tilburg Universiteit08:59

Next service: tomorrow 07:50 from Weert · Tue 10 Nov

Next departure 07:50 tomorrow · Weert
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 6 full · 9 partial · 15 no data
On-time · 90 days
85%
17/20 runs under 3 min
RT coverage: 6 full · 14 partial · 69 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
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

  • Fri 9 Oct Max en route +8 min · last fix heading to Tilburg +8 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Geldrop +5 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Tilburg +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 17
  • 3–10 min 15% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=2
  • 50% T n=2
  • 50% F n=2
  • 100% S n=5
  • 75% S n=4

Stops and timetable

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

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