Train NS 6451 Tilburg Universiteit – Weert
✓ Today’s run finished
Today, last fix heading to Maarheeze at 16:18 No data
- Tilburg Universiteit15:04
- Oisterwijk15:15
- Boxtel15:22
- Eindhoven Strijp-S15:35
- Geldrop15:52
- Maarheeze16:03
- Weert16:10
Next service: tomorrow 15:04 from Tilburg Universiteit · Sat 7 Nov
Last 30 days
Arrival delay at Weert, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Mon 5 Oct Max en route +6 min · last fix heading to Maarheeze +6 min
- Wed 4 Nov Max en route +4 min · last fix heading to Maarheeze +4 min
Distribution · 90 days
17 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 88% · 15
- 3–10 min 12% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 67% M n=3
- 100% T n=2
- 75% W n=4
- 100% T n=2
- 100% F n=1
- 100% S n=3
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 17 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 |
|---|---|---|---|
| 15:04 | on time | on time | |
| 15:08 / 15:09 | ≈ on time | ≈ on time | |
| 15:15 | ≈ on time | ≈ on time | |
| 15:22 / 15:23 | ≈ on time | ≈ on time | |
| 15:29 | ≈ on time | ≈ on time | |
| 15:35 | ≈ on time | ≈ +1 min | |
| 15:39 / 15:47 | ≈ on time | ≈ +1 min | |
| 15:52 | ≈ +1 min | ≈ +1 min | |
| 15:56 | ≈ +1 min | ≈ +1 min | |
| 16:03 | ≈ +1 min | ≈ +1 min | |
| 16:10 | +1 min | +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 |
|---|---|---|---|
| Fri 6 Nov | Maarheeze 16:18 | No data | — |
| Thu 5 Nov | Maarheeze 16:18 | No data | — |
| Wed 4 Nov | Maarheeze 16:19Partial coverage | +4 min | +4 min |
| Tue 3 Nov | Maarheeze 16:19 | No data | — |
| Mon 2 Nov | Maarheeze 16:19 | No data | — |
| Sat 31 Oct | Maarheeze 16:19 | +1 min | — |
| Fri 30 Oct | Maarheeze 16:23 | No data | — |
| Thu 29 Oct | Maarheeze 16:18Partial coverage | 0 min | — |
| Wed 28 Oct | Maarheeze 16:18Partial coverage | 0 min | — |
| Tue 27 Oct | Maarheeze 16:18 | No data | — |
| Mon 26 Oct | Maarheeze 16:19 | No data | — |
| Sun 25 Oct | Eindhoven Strijp-S 15:50 | No data | — |
| Sat 24 Oct | Maarheeze 16:19Partial coverage | +2 min | +2 min |
| Fri 23 Oct | Maarheeze 16:19 | No data | — |
| Thu 22 Oct | Maarheeze 16:19 | No data | — |
| Wed 21 Oct | Maarheeze 16:46Partial coverage | 0 min | — |
| Tue 20 Oct | Maarheeze 16:18Partial coverage | 0 min | — |
| Mon 19 Oct | Maarheeze 16:19Partial coverage | 0 min | — |
| Sun 18 Oct | Eindhoven Strijp-S 15:50 | 0 min | — |
| Sat 17 Oct | Maarheeze 16:18 | No data | — |
| Fri 16 Oct | Maarheeze 16:18 | No data | — |
| Thu 15 Oct | Maarheeze 16:18 | No data | — |
| Wed 14 Oct | Maarheeze 16:18 | No data | — |
| Tue 13 Oct | Maarheeze 16:18 | No data | — |
| Mon 12 Oct | Maarheeze 16:18Partial coverage | 0 min | — |
| Sun 11 Oct | Oisterwijk 15:52 | +1 min | +1 min |
| Sat 10 Oct | Maarheeze 16:18 | +1 min | — |
| Fri 9 Oct | Maarheeze 16:18 | +1 min | — |
| Thu 8 Oct | Maarheeze 16:18Partial coverage | +1 min | — |
| Wed 7 Oct | Maarheeze 16:18Partial coverage | 0 min | — |