Train NS 6449 Tilburg Universiteit – Weert
It has not run yet today
Last recorded run: Thursday 5 November No data
Next service: today 14:34 from Tilburg Universiteit · Fri 6 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
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 100% · 18
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=2
- 100% W n=4
- 100% T n=1
- 100% F n=2
- 100% S n=2
- 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 |
|---|---|---|---|
| 14:34 | on time | on time | |
| 14:38 / 14:39 | — | — | |
| 14:45 | — | — | |
| 14:52 / 14:53 | — | — | |
| 14:59 | — | — | |
| 15:05 | — | — | |
| 15:09 / 15:17 | — | — | |
| 15:22 | — | — | |
| 15:26 | — | — | |
| 15:33 | — | — | |
| 15:40 | — | — |
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 |
|---|---|---|---|
| Thu 5 Nov | Maarheeze 15:48 | No data | — |
| Wed 4 Nov | Maarheeze 15:48Partial coverage | +1 min | — |
| Tue 3 Nov | Maarheeze 15:48 | No data | — |
| Mon 2 Nov | Maarheeze 15:52 | 0 min | — |
| Sun 1 Nov | Maarheeze 15:50 | +1 min | — |
| Sat 31 Oct | Maarheeze 15:48 | No data | — |
| Fri 30 Oct | Maarheeze 15:48 | No data | — |
| Thu 29 Oct | Maarheeze 15:48 | No data | — |
| Wed 28 Oct | Maarheeze 15:48 | No data | — |
| Tue 27 Oct | Maarheeze 15:53Partial coverage | 0 min | — |
| Mon 26 Oct | Maarheeze 15:48Partial coverage | 0 min | — |
| Sun 25 Oct | Maarheeze 15:49 | No data | — |
| Sat 24 Oct | Maarheeze 15:48Partial coverage | +1 min | — |
| Fri 23 Oct | Maarheeze 15:48Partial coverage | 0 min | — |
| Thu 22 Oct | Maarheeze 15:48 | No data | — |
| Wed 21 Oct | Maarheeze 15:48Partial coverage | 0 min | — |
| Tue 20 Oct | Maarheeze 15:48 | No data | — |
| Mon 19 Oct | Maarheeze 15:50 | No data | — |
| Sun 18 Oct | Maarheeze 15:48Partial coverage | 0 min | — |
| Sat 17 Oct | Maarheeze 15:49 | No data | — |
| Fri 16 Oct | Maarheeze 15:48 | No data | — |
| Thu 15 Oct | Maarheeze 15:48 | No data | — |
| Wed 14 Oct | Maarheeze 15:48Partial coverage | 0 min | — |
| Tue 13 Oct | Maarheeze 15:48 | No data | — |
| Mon 12 Oct | Maarheeze 15:48Partial coverage | +1 min | — |
| Sun 11 Oct | Maarheeze 15:49Partial coverage | 0 min | — |
| Sat 10 Oct | Maarheeze 15:48Partial coverage | 0 min | — |
| Fri 9 Oct | Maarheeze 15:48Partial coverage | 0 min | +1 min |
| Thu 8 Oct | Maarheeze 15:48Partial coverage | 0 min | — |
| Wed 7 Oct | Maarheeze 15:48Partial coverage | +1 min | — |