Train NS 3677 Zwolle – Goes

Zwolle 21:20 → Goes 00:51 Daily 3 h 31 min · 20 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 21:20 from Zwolle · Fri 20 Nov

Next departure 21:20 today · Zwolle
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 22 full · 0 partial · 1 no data
On-time · 90 days
84%
31/37 runs under 3 min
RT coverage: 37 full · 0 partial · 15 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Tue 10 Nov Max en route +27 min · last fix heading to — +27 min
  • Fri 9 Oct Max en route +5 min · last fix heading to — +5 min
  • Wed 4 Nov Max en route +4 min · last fix heading to — +4 min
  • Fri 16 Oct Max en route +4 min · last fix heading to — +4 min
  • Fri 23 Oct Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 31
  • 3–10 min 14% · 5
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 75% T n=4
  • 67% W n=6
  • 100% T n=5
  • 50% F n=6
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 37 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
21:20on time on time
21:30≈ on time ≈ on time
21:36≈ on time ≈ on time
21:44 / 21:45≈ on time ≈ on time
21:56 / 21:58≈ on time ≈ +1 min
22:07≈ on time ≈ +1 min
22:19 / 22:23≈ on time ≈ +1 min
22:35 / 22:38≈ on time ≈ +1 min
22:53 / 22:54≈ on time ≈ +1 min
23:06 / 23:11≈ on time ≈ +2 min
23:26 / 23:28≈ on time ≈ +2 min
23:40 / 23:45≈ on time ≈ +2 min
23:53≈ on time ≈ +2 min
00:03 / 00:09≈ on time ≈ +3 min
00:18≈ on time ≈ +3 min
00:29≈ on time ≈ +3 min
00:33≈ on time ≈ +3 min
00:39≈ on time ≈ +3 min
00:45≈ on time ≈ +3 min
00:51on time +3 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 19 Nov— 01:340 min+19 min
Wed 18 Nov— 23:090 min—
Mon 16 NovOlst 22:340 min—
Sun 15 NovRilland-Bath 01:190 min+9 min
Sat 14 NovOss 01:040 min—
Fri 13 Nov— 01:070 min+7 min
Wed 11 Nov— 01:090 min—
Tue 10 Nov— 02:04+27 min+27 min
Mon 9 Nov— 00:040 min—
Sun 8 NovOss 23:090 min—
Sat 7 NovOss 23:08+2 min+2 min
Fri 6 Nov— 01:120 min—
Thu 5 Nov— 01:18No data—
Wed 4 Nov— 00:23+4 min+4 min
Sun 1 NovVlissingen Souburg 01:190 min—
Sat 31 Oct's-Hertogenbosch 23:250 min—
Fri 30 Oct— 01:150 min—
Thu 29 Oct— 01:160 min—
Wed 28 Oct— 01:160 min—
Tue 27 Oct— 01:140 min—
Mon 26 Oct— 01:110 min—
Fri 23 Oct— 01:18+3 min+4 min
Thu 22 Oct— 01:300 min—
Wed 21 Oct— 01:12No data—
Tue 20 Oct— 01:180 min—
Mon 19 Oct— 22:540 min—
Sun 18 OctVlissingen Souburg 01:220 min—
Sat 17 OctVlissingen Souburg 01:280 min—
Fri 16 Oct— 01:20+4 min+4 min
Thu 15 Oct— 01:120 min—