Train NS 3628 Goes – Zwolle

Goes 09:13 → Zwolle 12:40 Daily 3 h 27 min · 20 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Wijhe at 12:49 +5 min

  1. Goes09:13
  2. Krabbendijke09:30
  3. Roosendaal09:54
  4. 's-Hertogenbosch10:49
  5. Arnhem Centraal11:37
  6. Wijhe12:29
  7. Zwolle12:40

Next service: tomorrow 09:13 from Goes · Sun 15 Nov

Next departure 09:13 tomorrow · Goes
On-time · 30 days
80%
16/20 runs under 3 min
RT coverage: 19 full · 1 partial · 8 no data
On-time · 90 days
78%
21/27 runs under 3 min
RT coverage: 26 full · 1 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +4 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 9 Oct Max en route +12 min · last fix heading to Wijhe +12 min
  • Sun 18 Oct Max en route +6 min · last fix heading to Wijhe +5 min
  • Sat 14 Nov Max en route +6 min · last fix heading to Wijhe +5 min
  • Thu 12 Nov Max en route +5 min · last fix heading to Wijhe +4 min
  • Tue 10 Nov Max en route +6 min · last fix heading to Wijhe +4 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 78% · 21
  • 3–10 min 19% · 5
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (20 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
09:13on time on time
09:18≈ on time ≈ on time
09:24≈ on time ≈ on time
09:30≈ on time ≈ on time
09:35≈ on time ≈ +1 min
09:45≈ on time ≈ +1 min
09:54 / 09:57≈ on time ≈ +1 min
10:07≈ on time ≈ +1 min
10:15 / 10:19≈ on time ≈ +1 min
10:32 / 10:34≈ on time ≈ +2 min
10:49 / 10:55≈ on time ≈ +2 min
11:07≈ on time ≈ +3 min
11:23 / 11:24≈ on time ≈ +3 min
11:37 / 11:41≈ on time ≈ +3 min
11:52 / 11:53≈ on time ≈ +4 min
12:02 / 12:03≈ on time ≈ +4 min
12:15 / 12:16≈ on time ≈ +4 min
12:23≈ on time ≈ +4 min
12:29≈ on time ≈ +4 min
12:40on 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
Sat 14 NovWijhe 12:49Partial coverage+5 min+6 min
Fri 13 NovWijhe 12:440 min+2 min
Thu 12 NovWijhe 12:48+4 min+5 min
Wed 11 NovWijhe 12:430 min—
Tue 10 NovWijhe 12:49+4 min+6 min
Mon 9 NovWijhe 12:430 min—
Sun 8 NovWijhe 12:430 min—
Sat 7 NovWijhe 12:44+1 min+3 min
Fri 6 NovWijhe 12:43No data—
Thu 5 NovWijhe 12:44No data—
Wed 4 NovWijhe 12:44+1 min+2 min
Tue 3 NovWijhe 12:47No data—
Mon 2 NovWijhe 12:520 min—
Sun 1 NovWijhe 12:46+2 min+2 min
Sat 31 OctWijhe 12:450 min+2 min
Fri 30 OctWijhe 12:45No data—
Thu 29 OctArnhem Zuid 12:020 min—
Wed 28 OctArnhem Zuid 11:520 min—
Tue 27 OctArnhem Zuid 11:52No data—
Mon 26 OctArnhem Zuid 11:520 min—
Fri 23 OctNijmegen 11:440 min—
Thu 22 OctNijmegen 11:41No data—
Wed 21 OctNijmegen 11:47No data—
Tue 20 OctNijmegen 11:430 min—
Mon 19 OctWijhe 12:440 min—
Sun 18 OctWijhe 12:49+5 min+6 min
Sat 17 OctWijhe 12:440 min—
Fri 16 OctWijhe 12:48No data—
Thu 15 OctWijhe 12:44No data—
Wed 14 OctWijhe 12:45No data—