Train NS 3678 Vlissingen – Zutphen

Vlissingen 21:20 → Zutphen 00:32 Daily 3 h 12 min · 20 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +4 min

Next service: today 21:20 from Vlissingen · Thu 5 Nov

Full trip card
Next departure 21:20 today · Vlissingen
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 20 full · 3 partial · 4 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 21 full · 4 partial · 22 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 Zutphen, 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 4 Nov Max en route +5 min · last fix heading to — +4 min
  • Mon 2 Nov Max en route +3 min · last fix heading to — +3 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 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (20 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
Vlissingen
21:20on time on time
Vlissingen Souburg
21:24≈ on time ≈ on time
Middelburg
21:29≈ on time ≈ on time
Arnemuiden
21:33≈ on time ≈ on time
Goes
21:43 / 21:44≈ on time ≈ on time
Kapelle-Biezelinge
21:49≈ on time ≈ on time
Kruiningen-Yerseke
21:54≈ on time ≈ on time
Krabbendijke
22:00≈ on time ≈ +1 min
Rilland-Bath
22:04≈ on time ≈ +1 min
Bergen op Zoom
22:14≈ on time ≈ +1 min
Roosendaal
22:24 / 22:27≈ on time ≈ +1 min
Etten-Leur
22:37≈ on time ≈ +1 min
Breda
22:45 / 22:49≈ on time ≈ +1 min
Tilburg
23:02 / 23:04≈ on time ≈ +1 min
's-Hertogenbosch
23:19 / 23:25≈ on time ≈ +1 min
Oss
23:36≈ on time ≈ +2 min
Nijmegen
23:53 / 23:54≈ on time ≈ +2 min
Arnhem Centraal
00:06 / 00:11≈ on time ≈ +2 min
Dieren
00:22 / 00:23≈ on time ≈ +2 min
Zutphen
00:32on 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
Wed 4 Nov— 00:42+4 min+5 min
Mon 2 Nov— 00:39+3 min+3 min
Sun 1 NovDieren 00:38Partial coverage+1 min—
Sat 31 OctTilburg 23:280 min—
Fri 30 Oct— 00:330 min—
Thu 29 Oct— 00:150 min—
Wed 28 Oct— 00:160 min—
Mon 26 Oct— 00:160 min—
Sun 25 OctDieren 00:400 min—
Sat 24 OctEtten-Leur 00:340 min—
Fri 23 Oct— 00:390 min+3 min
Thu 22 Oct— 00:330 min—
Wed 21 Oct— 00:33No data—
Tue 20 Oct— 00:330 min—
Mon 19 Oct— 23:23No data—
Sun 18 OctDieren 00:37Partial coverage0 min—
Sat 17 OctDieren 00:37No data—
Fri 16 Oct— 00:38+2 min+2 min
Thu 15 Oct— 22:30No data—
Wed 14 Oct— 00:350 min—
Tue 13 Oct— 00:360 min—
Mon 12 Oct— 00:340 min+2 min
Sun 11 OctDieren 00:380 min+1 min
Sat 10 OctRilland-Bath 22:18Partial coverage0 min—
Fri 9 Oct— 00:34+1 min+1 min
Thu 8 Oct— 00:330 min—
Wed 7 Oct— 00:330 min—
Tue 6 Oct— 00:330 min—
Mon 5 OctArnhem Centraal 00:36Partial coverage+2 min+2 min
Sun 4 OctDieren 00:38No data—