Train NS 4088 Gouda – Gouda Goverwelle

Gouda 00:49 → Gouda Goverwelle 00:52 Daily 0 h 03 min · 2 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 00:53 0 min

  1. Gouda00:49
  2. Gouda Goverwelle00:52

Next service: tomorrow 00:49 from Gouda · Sun 8 Nov

Next departure 00:49 tomorrow · Gouda
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 2 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 12 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Gouda Goverwelle, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

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 100% · 23
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (2 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
00:49on time on time
00:52on time on time

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 7 Nov— 00:530 min—
Fri 6 Nov— 00:53No data—
Thu 5 Nov— 00:540 min—
Tue 3 Nov— 00:570 min—
Mon 2 NovGouda 01:030 min—
Sun 1 Nov— 01:480 min—
Sat 31 Oct— 01:090 min—
Fri 30 Oct— 00:580 min—
Thu 29 Oct— 00:530 min—
Wed 28 Oct— 00:540 min—
Tue 27 Oct— 00:530 min—
Sun 25 Oct— 00:560 min—
Sun 18 Oct— 02:07No data—
Sat 17 Oct— 00:530 min—
Fri 16 Oct— 00:530 min—
Thu 15 Oct— 00:530 min—
Wed 14 Oct— 00:530 min—
Tue 13 Oct— 00:560 min+1 min
Mon 12 OctGouda 01:030 min—
Sun 11 Oct— 00:540 min—
Sat 10 Oct— 00:530 min—
Fri 9 Oct— 00:560 min—
Thu 8 Oct— 00:530 min—
Wed 7 Oct— 00:530 min—
Tue 6 Oct— 00:530 min—
Mon 5 OctGouda 01:06No data—
Sun 4 OctRotterdam Alexander 00:48No data—
Mon 28 SeptGouda 01:04No data—
Mon 21 SeptGouda 01:03No data—
Mon 14 SeptGouda 01:03No data—