Train NS 6420 Weert – Tilburg Universiteit

Weert 05:50 → Tilburg Universiteit 06: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 07:09 0 min

  1. Weert05:50
  2. Heeze06:03
  3. Geldrop06:07
  4. Eindhoven Strijp-S06:24
  5. Boxtel06:37
  6. Tilburg06:50
  7. Tilburg Universiteit06:59

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

Next departure 05:50 tomorrow · Weert
On-time · 30 days
88%
21/24 runs under 3 min
RT coverage: 15 full · 9 partial · 1 no data
On-time · 90 days
88%
22/25 runs under 3 min
RT coverage: 16 full · 9 partial · 50 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: +3 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

  • Wed 28 Oct Max en route +16 min · last fix heading to Tilburg +15 min
  • Tue 27 Oct Max en route +7 min · last fix heading to Tilburg +5 min
  • Tue 13 Oct Max en route +6 min · last fix heading to Tilburg +4 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 88% · 22
  • 3–10 min 8% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 60% T n=5
  • 80% W n=5
  • 100% T n=5
  • 100% F n=4
  • 100% S n=3
  • — 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
05:50on time on time
05:56≈ on time ≈ on time
06:03≈ on time ≈ +1 min
06:07≈ on time ≈ +1 min
06:13 / 06:21≈ on time ≈ +2 min
06:24≈ on time ≈ +2 min
06:30≈ on time ≈ +3 min
06:37≈ on time ≈ +3 min
06:44≈ on time ≈ +4 min
06:50 / 06:54≈ on time ≈ +4 min
06:59on time +5 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
Thu 5 NovTilburg 07:09Partial coverage0 min—
Wed 4 NovTilburg 07:080 min—
Tue 3 NovTilburg 07:09+1 min—
Mon 2 NovTilburg 07:12No data—
Fri 30 OctTilburg 07:10Partial coverage+1 min+2 min
Thu 29 OctTilburg 07:09Partial coverage+1 min—
Wed 28 OctTilburg 07:23+15 min+16 min
Tue 27 OctTilburg 07:14+5 min+7 min
Mon 26 OctTilburg 07:080 min—
Sat 24 OctTilburg 07:090 min—
Fri 23 OctTilburg 07:09Partial coverage0 min—
Thu 22 OctTilburg 07:09Partial coverage0 min—
Wed 21 OctTilburg 07:080 min—
Tue 20 OctTilburg 07:090 min—
Mon 19 OctTilburg 07:10+1 min+2 min
Sat 17 OctTilburg 07:080 min—
Fri 16 OctTilburg 07:08Partial coverage0 min—
Thu 15 OctTilburg 07:08Partial coverage0 min—
Wed 14 OctTilburg 07:090 min—
Tue 13 OctTilburg 07:13+4 min+6 min
Mon 12 OctTilburg 07:080 min+1 min
Sat 10 OctTilburg 07:090 min—
Fri 9 OctTilburg 07:09Partial coverage0 min—
Thu 8 OctTilburg 07:09Partial coverage+1 min+1 min
Wed 7 OctTilburg 07:090 min—
Tue 6 OctTilburg 07:080 min—
Mon 5 OctTilburg 07:09No data—
Sat 3 OctTilburg 07:09No data—
Fri 2 OctTilburg 07:08No data—
Thu 1 OctTilburg 07:09No data—