Train NS 3634 Vlissingen – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Wijhe at 14:14 0 min

  1. Vlissingen10:18
  2. Goes10:41
  3. Rilland-Bath11:02
  4. Breda11:45
  5. Oss12:35
  6. Wijhe13:59
  7. Zwolle14:10

Next service: tomorrow 10:18 from Vlissingen · Thu 12 Nov

Next departure 10:18 tomorrow · Vlissingen
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 14 full · 6 partial · 8 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 17 full · 10 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Sat 10 Oct Max en route +12 min · last fix heading to Wijhe +10 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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