Train NS 6518 Deurne – Oss

Deurne 06:07 → Oss 07:25 Mon, Tue, Wed, Thu, Fri, Sat 1 h 18 min · 12 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to 's-Hertogenbosch at 07:28 0 min

  1. Deurne06:07
  2. Helmond06:16
  3. Helmond Brandevoort06:21
  4. Eindhoven Strijp-S06:39
  5. Best06:44
  6. 's-Hertogenbosch07:03
  7. Oss07:25

Next service: tomorrow 06:07 from Deurne · Fri 6 Nov

Next departure 06:07 tomorrow · Deurne
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 11 full · 13 partial · 1 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 11 full · 14 partial · 51 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

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

  • Fri 30 Oct Max en route +21 min · last fix heading to Vught +21 min
  • Thu 8 Oct Max en route +4 min · last fix heading to 's-Hertogenbosch +4 min

Distribution · 90 days

25 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 92% · 23
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=5
  • 80% T n=5
  • 75% F n=4
  • 100% S n=3
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (12 stops).

Last 90 days, 25 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.

StopSched.Usually 9 days in 10
06:07on time on time
06:12≈ on time ≈ on time
06:16≈ on time ≈ on time
06:19≈ on time ≈ on time
06:21≈ on time ≈ +1 min
06:29 / 06:35≈ on time ≈ +1 min
06:39≈ on time ≈ +1 min
06:44≈ on time ≈ +1 min
06:51≈ on time ≈ +2 min
06:58≈ on time ≈ +2 min
07:03 / 07:14≈ on time ≈ +2 min
07:25on time +3 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

DateLast stopFinalMax
Thu 5 Nov's-Hertogenbosch 07:28Partial coverage0 min—
Wed 4 Nov's-Hertogenbosch 07:28Partial coverage0 min—
Tue 3 Nov's-Hertogenbosch 07:28Partial coverage0 min—
Mon 2 Nov's-Hertogenbosch 07:28No data—
Fri 30 OctVught 07:30+21 min+21 min
Thu 29 Oct's-Hertogenbosch 07:32+3 min+3 min
Wed 28 Oct's-Hertogenbosch 07:290 min—
Tue 27 Oct's-Hertogenbosch 07:290 min—
Mon 26 Oct's-Hertogenbosch 07:290 min—
Sat 24 OctHelmond Brandevoort 06:38+1 min+2 min
Fri 23 OctVught 07:14+2 min+2 min
Thu 22 Oct's-Hertogenbosch 07:28Partial coverage0 min—
Wed 21 Oct's-Hertogenbosch 07:28Partial coverage0 min—
Tue 20 Oct's-Hertogenbosch 07:28Partial coverage0 min—
Mon 19 Oct's-Hertogenbosch 07:28Partial coverage0 min—
Sat 17 OctHelmond Brandevoort 06:37+1 min+1 min
Fri 16 OctVught 07:120 min—
Thu 15 Oct's-Hertogenbosch 07:28Partial coverage0 min—
Wed 14 Oct's-Hertogenbosch 07:37Partial coverage0 min—
Tue 13 Oct's-Hertogenbosch 07:28Partial coverage0 min—
Mon 12 Oct's-Hertogenbosch 07:29Partial coverage0 min—
Sat 10 OctHelmond Brandevoort 06:360 min—
Fri 9 OctVught 07:120 min—
Thu 8 Oct's-Hertogenbosch 07:28Partial coverage+4 min+4 min
Wed 7 Oct's-Hertogenbosch 07:28Partial coverage0 min—
Tue 6 Oct's-Hertogenbosch 07:28Partial coverage0 min—
Mon 5 Oct's-Hertogenbosch 07:29No data—
Sat 3 OctHelmond Brandevoort 06:36No data—
Fri 2 OctVught 07:13No data—
Thu 1 Oct's-Hertogenbosch 07:28No data—