Train NS 3607 Breda – Goes

Breda 06:15 → Goes 07:21 Mon, Tue, Wed, Thu, Fri, Sat 1 h 06 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November +9 min

Next service: today 06:15 from Breda · Tue 17 Nov

Next departure 06:15 today · Breda
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 19 full · 1 partial · 2 no data
On-time · 90 days
86%
24/28 runs under 3 min
RT coverage: 27 full · 1 partial · 35 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Goes, 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 16 Nov Max en route +9 min · last fix heading to Kapelle-Biezelinge +9 min
  • Thu 12 Nov Max en route +6 min · last fix heading to Etten-Leur +6 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Etten-Leur +3 min
  • Tue 13 Oct Max en route +3 min · last fix heading to Etten-Leur +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 24
  • 3–10 min 14% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 83% T n=6
  • 83% W n=6
  • 75% T n=4
  • 100% F n=5
  • 100% S n=1
  • — S n=0

Stops and timetable

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

Last 90 days, 28 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:15on time on time
06:22≈ on time ≈ on time
06:33 / 06:39≈ on time ≈ +1 min
06:48≈ on time ≈ +1 min
06:59≈ on time ≈ +2 min
07:03≈ on time ≈ +2 min
07:09≈ on time ≈ +2 min
07:15≈ on time ≈ +2 min
07:21on 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
Mon 16 NovKapelle-Biezelinge 07:38Partial coverage+9 min+9 min
Sat 14 NovKapelle-Biezelinge 07:280 min—
Fri 13 NovEtten-Leur 06:390 min—
Thu 12 NovEtten-Leur 06:44+6 min+6 min
Wed 11 NovEtten-Leur 06:39+1 min+1 min
Tue 10 NovEtten-Leur 06:390 min—
Mon 9 NovEtten-Leur 06:39+2 min+2 min
Fri 6 NovEtten-Leur 06:44No data—
Thu 5 NovEtten-Leur 06:39No data—
Wed 4 NovEtten-Leur 06:42+3 min+3 min
Tue 3 NovEtten-Leur 06:390 min—
Mon 2 NovEtten-Leur 06:390 min—
Fri 30 OctEtten-Leur 06:40+1 min—
Thu 29 OctEtten-Leur 06:390 min—
Wed 28 OctEtten-Leur 06:40+1 min—
Tue 27 OctEtten-Leur 06:390 min—
Mon 26 OctEtten-Leur 06:390 min—
Fri 23 OctEtten-Leur 06:390 min—
Thu 22 OctEtten-Leur 06:390 min—
Wed 21 OctEtten-Leur 06:40+1 min+1 min
Tue 20 OctEtten-Leur 06:42+2 min+3 min
Mon 19 OctEtten-Leur 06:390 min—
Fri 16 OctEtten-Leur 06:400 min+1 min
Thu 15 OctEtten-Leur 06:390 min—
Wed 14 OctEtten-Leur 06:40+1 min—
Tue 13 OctEtten-Leur 06:41+3 min+3 min
Mon 12 OctEtten-Leur 06:390 min—
Fri 9 OctEtten-Leur 06:380 min—
Thu 8 OctEtten-Leur 06:40No data—
Wed 7 OctEtten-Leur 06:390 min—