Train NS 2284 Vlissingen – Rotterdam Centraal

Vlissingen 22:51 → Rotterdam Centraal 00:38 Mon, Tue, Wed, Thu, Fri, Sat 1 h 47 min · 14 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 22:51 from Vlissingen · Wed 11 Nov

Full trip card
Next departure 22:51 today · Vlissingen
On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 25 full · 0 partial · 0 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 33 full · 0 partial · 10 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 Rotterdam Centraal, 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

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

  • Early 0% · 0
  • On time 100% · 33
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 33 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
Vlissingen
22:51on time on time
Vlissingen Souburg
22:55≈ on time ≈ on time
Middelburg
22:59≈ on time ≈ on time
Arnemuiden
23:04≈ on time ≈ on time
Goes
23:13 / 23:14≈ on time ≈ on time
Kapelle-Biezelinge
23:19≈ on time ≈ on time
Kruiningen-Yerseke
23:24≈ on time ≈ on time
Krabbendijke
23:30≈ on time ≈ on time
Rilland-Bath
23:34≈ on time ≈ on time
Bergen op Zoom
23:44 / 23:45≈ on time ≈ on time
Roosendaal
23:54 / 00:01≈ on time ≈ on time
Dordrecht
00:23 / 00:24≈ on time ≈ on time
Rotterdam Blaak
00:35≈ on time ≈ on time
Rotterdam Centraal
00:38on 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
Mon 9 Nov— 00:440 min—
Sun 8 Nov— 01:54+1 min—
Fri 6 Nov— 00:520 min—
Thu 5 Nov— 00:420 min—
Wed 4 Nov— 00:440 min+2 min
Tue 3 Nov— 00:540 min—
Sun 1 NovRotterdam Blaak 00:490 min—
Sat 31 OctKapelle-Biezelinge 01:090 min—
Fri 30 Oct— 02:330 min—
Thu 29 Oct— 00:390 min—
Wed 28 Oct— 00:520 min—
Tue 27 Oct— 00:390 min—
Mon 26 Oct— 00:390 min—
Sun 25 OctRotterdam Blaak 00:510 min—
Fri 23 Oct— 01:590 min—
Thu 22 Oct— 00:400 min—
Wed 21 Oct— 00:400 min—
Tue 20 Oct— 00:390 min—
Mon 19 Oct— 00:440 min—
Sun 18 OctRotterdam Blaak 00:500 min—
Sat 17 OctHeemstede-Aerdenhout 01:570 min—
Fri 16 Oct— 01:56+1 min+1 min
Thu 15 Oct— 00:390 min—
Wed 14 Oct— 00:390 min—
Tue 13 Oct— 00:500 min—
Mon 12 Oct— 00:400 min—
Sun 11 OctRotterdam Blaak 00:490 min—
Sat 10 Oct— 00:400 min—
Fri 9 Oct— 01:570 min—
Thu 8 Oct— 00:430 min—