Train NS 3622 Vlissingen – Zwolle

Vlissingen 07:18 → Zwolle 11:10 Daily 3 h 52 min · 24 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Wijhe at 11:14 No data

  1. Vlissingen07:18
  2. Goes07:41
  3. Rilland-Bath08:02
  4. Breda08:45
  5. Oss09:35
  6. Wijhe10:59
  7. Zwolle11:10

Next service: tomorrow 07:18 from Vlissingen · Fri 6 Nov

Next departure 07:18 tomorrow · Vlissingen
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 17 full · 5 partial · 6 no data
On-time · 90 days
87%
20/23 runs under 3 min
RT coverage: 17 full · 6 partial · 64 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Sun 1 Nov Max en route +10 min · last fix heading to Wijhe +10 min
  • Wed 4 Nov Max en route +9 min · last fix heading to Wijhe +9 min
  • Sun 18 Oct Max en route +8 min · last fix heading to Wijhe +7 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 13% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 75% W n=4
  • 100% T n=2
  • 100% F n=4
  • 100% S n=3
  • 33% 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
07:18on time on time
07:22≈ on time ≈ on time
07:26≈ on time ≈ on time
07:31≈ on time ≈ on time
07:41≈ on time ≈ on time
07:46≈ on time ≈ +1 min
07:52≈ on time ≈ +1 min
07:58≈ on time ≈ +1 min
08:02≈ on time ≈ +1 min
08:12≈ on time ≈ +1 min
08:22 / 08:27≈ on time ≈ +1 min
08:37≈ on time ≈ +1 min
08:45 / 08:49≈ on time ≈ +2 min
09:02 / 09:04≈ on time ≈ +2 min
09:20 / 09:24≈ on time ≈ +2 min
09:35≈ on time ≈ +3 min
09:52 / 09:54≈ on time ≈ +3 min
10:07 / 10:11≈ on time ≈ +3 min
10:22 / 10:23≈ on time ≈ +3 min
10:32 / 10:33≈ on time ≈ +4 min
10:45 / 10:46≈ on time ≈ +4 min
10:53≈ on time ≈ +4 min
10:59≈ on time ≈ +4 min
11:10on time +4 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 NovWijhe 11:14No data—
Wed 4 NovWijhe 11:22Partial coverage+9 min+9 min
Tue 3 NovWijhe 11:17No data—
Mon 2 NovWijhe 11:18Partial coverage0 min—
Sun 1 NovWijhe 11:18+10 min+10 min
Sat 31 OctWijhe 11:16+1 min+3 min
Fri 30 OctWijhe 11:150 min—
Thu 29 OctArnhem Zuid 10:220 min—
Wed 28 OctArnhem Zuid 10:230 min—
Tue 27 OctArnhem Zuid 10:230 min—
Mon 26 OctArnhem Zuid 10:250 min—
Fri 23 OctNijmegen 10:100 min—
Thu 22 OctNijmegen 10:11No data—
Wed 21 OctNijmegen 10:110 min—
Tue 20 OctNijmegen 10:110 min—
Mon 19 OctWijhe 11:13Partial coverage0 min—
Sun 18 OctWijhe 11:21+7 min+8 min
Sat 17 OctWijhe 11:140 min—
Fri 16 OctWijhe 11:170 min—
Thu 15 OctWijhe 11:14No data—
Wed 14 OctWijhe 11:16No data—
Tue 13 OctWijhe 11:17No data—
Mon 12 OctWijhe 11:140 min—
Sun 11 OctWijhe 11:17+3 min+4 min
Sat 10 OctWijhe 11:16+2 min+3 min
Fri 9 OctWijhe 11:130 min—
Thu 8 OctWijhe 11:13Partial coverage+2 min+4 min
Wed 7 OctWijhe 12:01Partial coverage0 min—
Tue 6 OctWijhe 11:17Partial coverage+3 min+4 min
Mon 5 OctWijhe 11:15No data—