Train NS 6523 Oss – Deurne

Oss 07:31 → Deurne 08:58 Daily 1 h 27 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 07:31 from Oss · Fri 6 Nov

Next departure 07:31 today · Oss
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 12 full · 6 partial · 11 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 12 full · 8 partial · 67 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: +2 min

Last 30 days

Arrival delay at Deurne, 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 9 Oct Max en route +6 min · last fix heading to Helmond Brouwhuis +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=3
  • 100% T n=3
  • 0% F n=1
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 20 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
07:31on time on time
07:34≈ on time ≈ on time
07:41≈ on time ≈ on time
07:45≈ on time ≈ on time
07:49 / 07:58≈ on time ≈ on time
08:03≈ on time ≈ +1 min
08:09≈ on time ≈ +1 min
08:15≈ on time ≈ +1 min
08:21≈ on time ≈ +1 min
08:25 / 08:37≈ on time ≈ +1 min
08:43≈ on time ≈ +2 min
08:46≈ on time ≈ +2 min
08:50≈ on time ≈ +2 min
08:53≈ on time ≈ +2 min
08:58on time +2 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 NovHelmond Brouwhuis 09:09No data—
Wed 4 NovHelmond Brouwhuis 09:09Partial coverage+2 min+2 min
Tue 3 NovHelmond Brouwhuis 09:09No data—
Mon 2 NovHelmond Brouwhuis 09:09Partial coverage0 min—
Sun 1 NovEindhoven Strijp-S 08:37+1 min+1 min
Sat 31 OctEindhoven Strijp-S 08:36No data—
Fri 30 OctEindhoven Strijp-S 08:37No data—
Thu 29 OctHelmond Brouwhuis 09:090 min—
Wed 28 OctHelmond Brouwhuis 09:090 min—
Tue 27 OctHelmond Brouwhuis 09:090 min—
Mon 26 OctHelmond Brouwhuis 09:120 min—
Sun 25 OctEindhoven Strijp-S 08:36No data—
Sat 24 OctHelmond Brouwhuis 09:10+2 min+2 min
Fri 23 OctHelmond Brouwhuis 09:09No data—
Thu 22 OctHelmond Brouwhuis 09:11Partial coverage0 min—
Wed 21 OctHelmond Brouwhuis 09:09No data—
Tue 20 OctHelmond Brouwhuis 09:080 min—
Mon 19 OctHelmond Brouwhuis 09:09Partial coverage0 min—
Sun 18 OctEindhoven Strijp-S 08:370 min+1 min
Sat 17 OctHelmond Brouwhuis 09:070 min—
Fri 16 OctHelmond Brouwhuis 09:07No data—
Thu 15 OctHelmond Brouwhuis 09:09No data—
Wed 14 OctHelmond Brouwhuis 09:09No data—
Tue 13 OctHelmond Brouwhuis 09:08No data—
Mon 12 OctHelmond Brouwhuis 09:10Partial coverage0 min—
Sun 11 OctEindhoven Strijp-S 08:36+1 min—
Sat 10 OctHelmond Brouwhuis 09:070 min—
Fri 9 OctHelmond Brouwhuis 09:15+6 min+6 min
Thu 8 OctHelmond Brouwhuis 09:09Partial coverage0 min—
Wed 7 OctHelmond Brouwhuis 09:08Partial coverage0 min—