Train NS 6423 Tilburg Universiteit – Weert
✓ Today’s run finished
Today, last fix heading to Maarheeze at 09:18 +1 min
- Tilburg Universiteit08:03
- Oisterwijk08:15
- Boxtel08:21
- Eindhoven Strijp-S08:35
- Geldrop08:52
- Maarheeze09:03
- Weert09:10
Next service: tomorrow 08:03 from Tilburg Universiteit · Mon 9 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
- Sat 7 Nov Max en route +5 min · last fix heading to Maarheeze +5 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 94% · 16
- 3–10 min 6% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=3
- 100% W n=3
- 100% T n=3
- 100% F n=1
- 80% S n=5
- 100% S n=1
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 |
|---|---|---|---|
| 08:03 | on time | on time | |
| 08:08 / 08:09 | ≈ on time | ≈ on time | |
| 08:15 | ≈ on time | ≈ on time | |
| 08:21 / 08:23 | ≈ on time | ≈ on time | |
| 08:29 | ≈ on time | ≈ +1 min | |
| 08:35 | ≈ on time | ≈ +1 min | |
| 08:39 / 08:47 | ≈ on time | ≈ +1 min | |
| 08:52 | ≈ on time | ≈ +1 min | |
| 08:56 | ≈ on time | ≈ +1 min | |
| 09:03 | ≈ on time | ≈ +1 min | |
| 09:10 | 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 |
|---|---|---|---|
| Sun 8 Nov | Maarheeze 09:18Partial coverage | +1 min | — |
| Sat 7 Nov | Maarheeze 09:23 | +5 min | +5 min |
| Fri 6 Nov | Maarheeze 09:17 | No data | — |
| Thu 5 Nov | Maarheeze 09:18 | No data | — |
| Wed 4 Nov | Maarheeze 09:18 | 0 min | — |
| Tue 3 Nov | Maarheeze 09:19 | No data | — |
| Mon 2 Nov | Maarheeze 09:18 | No data | — |
| Sat 31 Oct | Maarheeze 09:19 | +1 min | — |
| Fri 30 Oct | Maarheeze 09:18 | No data | — |
| Thu 29 Oct | Maarheeze 09:18 | 0 min | — |
| Wed 28 Oct | Maarheeze 09:18 | No data | — |
| Tue 27 Oct | Maarheeze 09:17 | 0 min | — |
| Mon 26 Oct | Maarheeze 09:18 | No data | — |
| Sat 24 Oct | Maarheeze 09:18 | 0 min | +1 min |
| Fri 23 Oct | Maarheeze 09:20 | No data | — |
| Thu 22 Oct | Maarheeze 09:19 | 0 min | — |
| Wed 21 Oct | Maarheeze 09:18 | 0 min | — |
| Tue 20 Oct | Maarheeze 09:18 | 0 min | — |
| Mon 19 Oct | Maarheeze 09:19 | 0 min | — |
| Sat 17 Oct | Maarheeze 09:20 | +2 min | +3 min |
| Fri 16 Oct | Maarheeze 09:18 | No data | — |
| Thu 15 Oct | Maarheeze 09:18 | No data | — |
| Wed 14 Oct | Maarheeze 09:17 | No data | — |
| Tue 13 Oct | Maarheeze 09:18 | No data | — |
| Mon 12 Oct | Maarheeze 09:18 | No data | — |
| Sat 10 Oct | Maarheeze 09:17 | 0 min | — |
| Fri 9 Oct | Maarheeze 09:18 | +1 min | +1 min |
| Thu 8 Oct | Maarheeze 09:18 | +1 min | — |
| Wed 7 Oct | Maarheeze 09:18 | 0 min | — |
| Tue 6 Oct | Maarheeze 09:18 | +1 min | — |