Train NS 3680 Roosendaal – Arnhem Centraal

Roosendaal 22:57 → Arnhem Centraal 00:37 Daily 1 h 40 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 22:57 from Roosendaal · Fri 6 Nov

Full trip card
Next departure 22:57 today · Roosendaal
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 19 full · 4 partial · 4 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 21 full · 5 partial · 20 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: +1 min

Last 30 days

Arrival delay at Arnhem Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 12 Oct Max en route +5 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 100% W n=3
  • 100% T n=2
  • 100% F n=3
  • 100% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 26 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
Roosendaal
22:57on time on time
Etten-Leur
23:07≈ on time ≈ on time
Breda
23:15 / 23:19≈ on time ≈ on time
Tilburg
23:32 / 23:34≈ on time ≈ +1 min
's-Hertogenbosch
23:49 / 23:55≈ on time ≈ +1 min
Oss
00:06≈ on time ≈ +1 min
Nijmegen
00:23 / 00:25≈ on time ≈ +1 min
Arnhem Centraal
00:37on 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

DateLast stopFinalMax
Thu 5 Nov— 00:39No data—
Wed 4 Nov— 00:390 min+1 min
Tue 3 Nov— 00:390 min—
Mon 2 Nov— 00:390 min—
Sun 1 NovNijmegen 00:490 min—
Sat 31 OctRoosendaal 00:21Partial coverage0 min—
Thu 29 Oct— 00:45+1 min—
Wed 28 Oct— 00:45No data—
Tue 27 Oct— 00:580 min—
Mon 26 Oct— 00:450 min—
Sun 25 OctNijmegen 01:210 min—
Sat 24 Oct— 01:030 min—
Fri 23 Oct— 00:510 min+7 min
Thu 22 Oct— 00:50No data—
Wed 21 Oct— 00:41No data—
Tue 20 Oct— 00:450 min—
Mon 19 Oct— 23:50+1 min+1 min
Sun 18 OctNijmegen 00:40Partial coverage+1 min+2 min
Sat 17 OctTilburg 00:45Partial coverage0 min—
Fri 16 Oct— 00:39+1 min+2 min
Wed 14 Oct— 00:380 min—
Tue 13 Oct— 01:030 min—
Mon 12 Oct— 00:47+3 min+5 min
Sun 11 OctNijmegen 00:41Partial coverage0 min—
Sat 10 Oct— 00:390 min—
Fri 9 Oct— 00:380 min—
Thu 8 Oct— 00:390 min+1 min
Wed 7 Oct— 00:390 min+1 min
Tue 6 Oct— 00:42+2 min+4 min
Mon 5 OctOss 00:43Partial coverage+2 min+4 min