Train NS 6418 Weert – Tilburg Universiteit

Weert 05:20 → Tilburg Universiteit 06:29 Mon, Tue, Wed, Thu, Fri 1 h 09 min · 11 stops NS (Nederlandse Spoorwegen)

Running now · updated 06:23

Heading to Tilburg Universiteit No data

Estimated arrival at Tilburg Universiteit 06:29 · 0 km/h

  1. Weert05:20
  2. Heeze05:33
  3. Geldrop05:37
  4. Eindhoven Strijp-S05:54
  5. Boxtel06:07
  6. Oisterwijk06:14
  7. Tilburg Universiteit06:29
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 14 full · 6 partial · 2 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 16 full · 6 partial · 43 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 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
  • 80% T n=5
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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 10Today
05:20on time on time
05:26≈ on time ≈ on time
05:33≈ on time ≈ on time
05:37≈ on time ≈ on time
05:43 / 05:51≈ on time ≈ on time
05:54≈ on time ≈ +1 min
06:00≈ on time ≈ +1 min
06:07≈ on time ≈ +1 min
06:14≈ on time ≈ +1 min
06:20 / 06:24≈ on time ≈ +1 min
06:29on time +1 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
Fri 6 NovTilburg 06:19No data—
Thu 5 NovTilburg 06:38Partial coverage+1 min+2 min
Wed 4 NovTilburg 06:380 min—
Tue 3 NovTilburg 06:380 min—
Mon 2 NovTilburg 06:39No data—
Fri 30 OctTilburg 06:380 min—
Thu 29 OctTilburg 06:38Partial coverage0 min—
Wed 28 OctTilburg 06:390 min—
Tue 27 OctTilburg 06:380 min—
Mon 26 OctTilburg 06:41+2 min+2 min
Fri 23 OctTilburg 06:41Partial coverage+2 min+4 min
Thu 22 OctTilburg 06:39Partial coverage0 min—
Wed 21 OctTilburg 06:390 min—
Tue 20 OctTilburg 06:40+1 min+2 min
Mon 19 OctTilburg 06:390 min—
Fri 16 OctTilburg 06:390 min—
Thu 15 OctTilburg 06:38Partial coverage0 min—
Wed 14 OctTilburg 06:470 min+7 min
Tue 13 OctTilburg 06:40+1 min+2 min
Mon 12 OctTilburg 06:400 min—
Fri 9 OctTilburg 06:390 min—
Thu 8 OctTilburg 06:44Partial coverage+5 min+5 min
Wed 7 OctTilburg 06:380 min—
Tue 6 OctTilburg 06:380 min—
Mon 5 OctTilburg 06:41No data—
Fri 2 OctTilburg 06:40No data—
Thu 1 OctTilburg 06:39No data—
Wed 30 SeptTilburg 06:38No data—
Tue 29 SeptTilburg 06:38No data—
Mon 28 SeptTilburg 06:48No data—