Train NS 3674 Vlissingen – Zwolle

Vlissingen 20:20 → Zwolle 00:10 Daily 3 h 50 min · 24 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

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

Next departure 20:20 today · Vlissingen
On-time · 30 days
86%
18/21 runs under 3 min
RT coverage: 18 full · 3 partial · 4 no data
On-time · 90 days
87%
20/23 runs under 3 min
RT coverage: 19 full · 4 partial · 26 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+9min
9 in 10 runs arrive with less than this
30 days: +11 min

Last 30 days

Arrival delay at Zwolle, 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 23 Oct Max en route +32 min · last fix heading to — +32 min
  • Mon 12 Oct Max en route +13 min · last fix heading to — +13 min
  • Fri 16 Oct Max en route +12 min · last fix heading to — +11 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 20
  • 3–10 min 0% · 0
  • 10–30 min 9% · 2
  • 30+ min 4% · 1

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
20:20on time on time
20:24≈ on time ≈ on time
20:29≈ on time ≈ on time
20:33≈ on time ≈ +1 min
20:43 / 20:44≈ on time ≈ +1 min
20:49≈ on time ≈ +1 min
20:54≈ on time ≈ +2 min
21:00≈ on time ≈ +2 min
21:04≈ on time ≈ +2 min
21:14≈ on time ≈ +3 min
21:24 / 21:27≈ on time ≈ +3 min
21:37≈ on time ≈ +4 min
21:45 / 21:49≈ on time ≈ +4 min
22:02 / 22:04≈ on time ≈ +5 min
22:19 / 22:25≈ on time ≈ +6 min
22:36≈ on time ≈ +7 min
22:53 / 22:54≈ on time ≈ +8 min
23:06 / 23:11≈ on time ≈ +8 min
23:22 / 23:23≈ on time ≈ +9 min
23:32 / 23:33≈ on time ≈ +10 min
23:45 / 23:46≈ on time ≈ +10 min
23:53≈ on time ≈ +11 min
23:59≈ on time ≈ +11 min
00:10on time +11 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:12+1 min+1 min
Sun 1 NovWijhe 00:14Partial coverage+2 min+2 min
Sat 31 OctArnhem Centraal 23:250 min—
Fri 30 Oct— 00:250 min—
Thu 29 Oct— 23:150 min—
Wed 28 Oct— 23:16No data—
Tue 27 Oct— 23:16No data—
Mon 26 Oct— 23:150 min—
Fri 23 Oct— 00:02+32 min+32 min
Thu 22 Oct— 23:130 min—
Wed 21 Oct— 23:11No data—
Tue 20 Oct— 23:100 min—
Mon 19 Oct— 22:210 min—
Sun 18 OctWijhe 00:16Partial coverage+1 min+3 min
Sat 17 OctWijhe 00:15Partial coverage0 min—
Fri 16 Oct— 00:35+11 min+12 min
Thu 15 Oct— 21:25No data—
Wed 14 Oct— 00:110 min—
Tue 13 Oct— 00:160 min—
Mon 12 Oct— 00:38+13 min+13 min
Sun 11 OctWijhe 00:14+1 min+1 min
Sat 10 OctTilburg 00:210 min+5 min
Fri 9 Oct— 23:10+2 min+2 min
Thu 8 Oct— 00:290 min+5 min
Wed 7 Oct— 00:110 min+1 min
Tue 6 Oct— 00:12+1 min—
Mon 5 OctWijhe 00:12Partial coverage0 min—
Sun 4 OctWijhe 00:14No data—
Sat 3 OctWijhe 00:11No data—
Sun 27 SeptWijhe 00:15No data—