Train NS 6520 Deurne – Oss
✓ Today’s run finished
Today, last fix heading to 's-Hertogenbosch at 07:58 0 min
- Deurne06:37
- Helmond06:46
- Helmond Brandevoort06:51
- Eindhoven Strijp-S07:09
- Best07:14
- 's-Hertogenbosch07:33
- Oss07:55
Next service: tomorrow 06:37 from Deurne · Fri 20 Nov
Last 30 days
Arrival delay at Oss, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 18 Nov Max en route +22 min · last fix heading to 's-Hertogenbosch +22 min
- Fri 30 Oct Max en route +9 min · last fix heading to Vught +9 min
Distribution · 90 days
41 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 95% · 39
- 3–10 min 2% · 1
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=7
- 86% W n=7
- 100% T n=6
- 80% F n=5
- 100% S n=6
- 100% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 41 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 |
|---|---|---|---|
| 06:37 | on time | on time | |
| 06:42 | ≈ on time | ≈ on time | |
| 06:46 | ≈ on time | ≈ on time | |
| 06:49 | ≈ on time | ≈ on time | |
| 06:51 | ≈ on time | ≈ on time | |
| 06:59 / 07:05 | ≈ on time | ≈ on time | |
| 07:09 | ≈ on time | ≈ +1 min | |
| 07:14 | ≈ on time | ≈ +1 min | |
| 07:21 | ≈ on time | ≈ +1 min | |
| 07:28 | ≈ on time | ≈ +1 min | |
| 07:33 / 07:43 | ≈ on time | ≈ +1 min | |
| 07:55 | 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 |
|---|---|---|---|
| Thu 19 Nov | 's-Hertogenbosch 07:58Partial coverage | 0 min | — |
| Wed 18 Nov | 's-Hertogenbosch 08:14Partial coverage | +22 min | +22 min |
| Tue 17 Nov | 's-Hertogenbosch 07:58Partial coverage | +2 min | +2 min |
| Mon 16 Nov | 's-Hertogenbosch 07:58Partial coverage | 0 min | — |
| Sun 15 Nov | Vught 07:42 | 0 min | — |
| Sat 14 Nov | Vught 07:42 | 0 min | — |
| Fri 13 Nov | Vught 07:42 | 0 min | — |
| Thu 12 Nov | 's-Hertogenbosch 07:57Partial coverage | 0 min | — |
| Wed 11 Nov | 's-Hertogenbosch 07:57Partial coverage | 0 min | — |
| Tue 10 Nov | 's-Hertogenbosch 07:58Partial coverage | +3 min | +3 min |
| Mon 9 Nov | 's-Hertogenbosch 07:58Partial coverage | +3 min | +3 min |
| Sun 8 Nov | Vught 07:42 | 0 min | — |
| Sat 7 Nov | Vught 07:43 | +1 min | +1 min |
| Fri 6 Nov | Vught 07:43 | No data | — |
| Thu 5 Nov | 's-Hertogenbosch 07:58 | No data | — |
| Wed 4 Nov | 's-Hertogenbosch 07:58Partial coverage | +1 min | +1 min |
| Tue 3 Nov | 's-Hertogenbosch 07:58Partial coverage | 0 min | — |
| Mon 2 Nov | 's-Hertogenbosch 07:58 | No data | — |
| Sun 1 Nov | Vught 07:43 | +1 min | — |
| Sat 31 Oct | Vught 07:43 | 0 min | — |
| Fri 30 Oct | Vught 07:52 | +9 min | +9 min |
| Thu 29 Oct | 's-Hertogenbosch 07:59 | 0 min | — |
| Wed 28 Oct | 's-Hertogenbosch 07:59 | 0 min | — |
| Tue 27 Oct | 's-Hertogenbosch 07:59 | 0 min | — |
| Mon 26 Oct | 's-Hertogenbosch 08:01 | +1 min | +1 min |
| Sun 25 Oct | Vught 07:42 | No data | — |
| Sat 24 Oct | Vught 07:43 | +1 min | +1 min |
| Fri 23 Oct | Vught 07:43 | +1 min | — |
| Thu 22 Oct | 's-Hertogenbosch 07:58Partial coverage | 0 min | — |
| Wed 21 Oct | 's-Hertogenbosch 07:58Partial coverage | 0 min | — |