Train NS 3647 Zwolle – Goes

Zwolle 13:50 → Goes 17:19 Daily 3 h 29 min · 20 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Kapelle-Biezelinge at 17:28 0 min

  1. Zwolle13:50
  2. Deventer14:14
  3. Arnhem Centraal14:49
  4. Tilburg15:56
  5. Roosendaal16:33
  6. Kapelle-Biezelinge17:13
  7. Goes17:19

Next service: tomorrow 13:50 from Zwolle · Sun 15 Nov

Next departure 13:50 tomorrow · Zwolle
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 19 full · 1 partial · 8 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 28 full · 1 partial · 58 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 Goes, 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 31 Oct Max en route +3 min · last fix heading to Etten-Leur +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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
13:50on time on time
13:59≈ on time ≈ on time
14:06≈ on time ≈ on time
14:14 / 14:15≈ on time ≈ on time
14:26 / 14:28≈ on time ≈ on time
14:37≈ on time ≈ on time
14:49 / 14:53≈ on time ≈ on time
15:05 / 15:08≈ on time ≈ +1 min
15:23 / 15:24≈ on time ≈ +1 min
15:36 / 15:41≈ on time ≈ +1 min
15:56 / 15:58≈ on time ≈ +1 min
16:10 / 16:15≈ on time ≈ +1 min
16:23≈ on time ≈ +1 min
16:33 / 16:37≈ on time ≈ +1 min
16:47≈ on time ≈ +1 min
16:57≈ on time ≈ +1 min
17:01≈ on time ≈ +1 min
17:07≈ on time ≈ +1 min
17:13≈ on time ≈ +1 min
17:19on 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
Sat 14 NovKapelle-Biezelinge 17:28Partial coverage0 min—
Fri 13 NovEtten-Leur 16:39+2 min+2 min
Thu 12 NovEtten-Leur 16:42+2 min+3 min
Wed 11 NovEtten-Leur 16:390 min—
Tue 10 NovEtten-Leur 16:390 min—
Mon 9 NovEtten-Leur 16:39+1 min+1 min
Sun 8 NovOss 15:380 min—
Sat 7 NovOss 15:380 min—
Fri 6 NovEtten-Leur 16:39No data—
Thu 5 NovEtten-Leur 16:39No data—
Wed 4 NovEtten-Leur 16:390 min—
Tue 3 NovEtten-Leur 16:39No data—
Mon 2 NovBreda 17:140 min—
Sun 1 NovEtten-Leur 16:400 min—
Sat 31 OctEtten-Leur 16:40+3 min+3 min
Fri 30 OctEtten-Leur 16:39No data—
Thu 29 OctEtten-Leur 16:390 min—
Wed 28 OctEtten-Leur 16:390 min—
Tue 27 OctEtten-Leur 16:390 min—
Mon 26 OctEtten-Leur 16:390 min—
Fri 23 OctEtten-Leur 16:40No data—
Thu 22 OctEtten-Leur 16:39No data—
Wed 21 OctEtten-Leur 16:40No data—
Tue 20 OctEtten-Leur 16:40No data—
Mon 19 OctEtten-Leur 16:400 min—
Sun 18 OctEtten-Leur 16:41+1 min—
Sat 17 OctEtten-Leur 16:400 min—
Fri 16 OctEtten-Leur 16:540 min—
Thu 15 OctEtten-Leur 16:39No data—
Wed 14 OctEtten-Leur 16:390 min—