Train NS 6466 Weert – Tilburg Universiteit
It has not run yet today
Last recorded run: Monday 9 November 0 min
Next service: today 17:20 from Weert · Tue 10 Nov
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 6 Nov Max en route +4 min · last fix heading to Tilburg +3 min
- Mon 5 Oct Max en route +3 min · last fix heading to Boxtel +3 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 16
- 3–10 min 11% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 80% M n=5
- 100% T n=1
- 100% W n=1
- 100% T n=1
- 67% F n=3
- 100% S n=4
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 18 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 17:20 | on time | on time | |
| 17:26 | ≈ on time | ≈ on time | |
| 17:33 | ≈ on time | ≈ on time | |
| 17:37 | ≈ on time | ≈ on time | |
| 17:43 / 17:51 | ≈ on time | ≈ on time | |
| 17:54 | ≈ on time | ≈ on time | |
| 18:00 | ≈ on time | ≈ on time | |
| 18:07 | ≈ on time | ≈ on time | |
| 18:14 | ≈ on time | ≈ +1 min | |
| 18:20 / 18:24 | ≈ on time | ≈ +1 min | |
| 18:29 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 9 Nov | Boxtel 18:29Partial coverage | 0 min | — |
| Sun 8 Nov | Tilburg 18:38 | 0 min | — |
| Sat 7 Nov | Tilburg 18:38 | 0 min | — |
| Fri 6 Nov | Tilburg 18:38 | +3 min | +4 min |
| Thu 5 Nov | Boxtel 18:19 | No data | — |
| Wed 4 Nov | Oisterwijk 18:29 | No data | — |
| Tue 3 Nov | Boxtel 18:29 | No data | — |
| Mon 2 Nov | Boxtel 18:29 | No data | — |
| Sat 31 Oct | Geldrop 17:52 | 0 min | — |
| Fri 30 Oct | Tilburg 18:38 | 0 min | — |
| Thu 29 Oct | Best 18:31 | No data | — |
| Wed 28 Oct | Boxtel 18:30Partial coverage | 0 min | — |
| Tue 27 Oct | Best 18:32 | No data | — |
| Mon 26 Oct | Boxtel 18:30Partial coverage | 0 min | — |
| Sun 25 Oct | Tilburg 18:39 | No data | — |
| Sat 24 Oct | Tilburg 18:38Partial coverage | 0 min | — |
| Fri 23 Oct | Tilburg 18:38 | No data | — |
| Thu 22 Oct | Tilburg 18:38 | No data | — |
| Wed 21 Oct | Tilburg 18:34 | No data | — |
| Tue 20 Oct | Tilburg 18:38 | No data | — |
| Mon 19 Oct | Tilburg 18:38Partial coverage | 0 min | — |
| Sun 18 Oct | Tilburg 18:38 | 0 min | — |
| Sat 17 Oct | Tilburg 18:38 | No data | — |
| Fri 16 Oct | Tilburg 18:39 | No data | — |
| Thu 15 Oct | Tilburg 18:40 | No data | — |
| Wed 14 Oct | Tilburg 18:38 | No data | — |
| Tue 13 Oct | Tilburg 18:38 | No data | — |
| Mon 12 Oct | Tilburg 18:38Partial coverage | 0 min | — |
| Sun 11 Oct | Tilburg 18:39 | 0 min | — |
| Sat 10 Oct | Tilburg 18:38 | 0 min | — |