Train NS 6633 Nijmegen – Zwijndrecht

Nijmegen 09:50 → Zwijndrecht 11:38 Daily 1 h 48 min · 20 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Dordrecht at 11:48 0 min

  1. Nijmegen09:50
  2. Wijchen10:01
  3. Oss West10:16
  4. Tilburg10:46
  5. Gilze-Rijen10:59
  6. Dordrecht11:32
  7. Zwijndrecht11:38

Next service: tomorrow 09:50 from Nijmegen · Mon 9 Nov

Next departure 09:50 tomorrow · Nijmegen
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 16 full · 1 partial · 13 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 20 full · 1 partial · 68 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 Zwijndrecht, 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=2
  • 100% T n=2
  • 100% F n=2
  • 100% 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, 21 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:50on time on time
09:53≈ on time ≈ on time
09:56≈ on time ≈ on time
10:01≈ on time ≈ on time
10:06≈ on time ≈ on time
10:12 / 10:13≈ on time ≈ on time
10:16≈ on time ≈ on time
10:23≈ on time ≈ on time
10:27≈ on time ≈ on time
10:30 / 10:32≈ on time ≈ on time
10:46 / 10:48≈ on time ≈ on time
10:51≈ on time ≈ on time
10:55≈ on time ≈ on time
10:59≈ on time ≈ on time
11:06 / 11:09≈ on time ≈ on time
11:13≈ on time ≈ on time
11:20≈ on time ≈ on time
11:28≈ on time ≈ on time
11:32 / 11:34≈ on time ≈ on time
11: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
Sun 8 NovDordrecht 11:48Partial coverage0 min—
Sat 7 NovDordrecht 11:480 min—
Fri 6 NovDordrecht Zuid 11:54No data—
Thu 5 NovDordrecht Zuid 11:42No data—
Wed 4 NovDordrecht Zuid 11:420 min+2 min
Tue 3 NovDordrecht Zuid 11:42No data—
Mon 2 NovDordrecht Zuid 11:420 min—
Sun 1 NovDordrecht Zuid 11:430 min—
Sat 31 OctDordrecht Zuid 11:420 min—
Fri 30 OctDordrecht Zuid 11:420 min—
Thu 29 OctDordrecht Zuid 11:420 min—
Wed 28 OctDordrecht Zuid 11:44No data—
Tue 27 OctDordrecht Zuid 11:420 min—
Mon 26 OctDordrecht Zuid 11:420 min—
Sun 25 OctDordrecht Zuid 11:42No data—
Sat 24 OctDordrecht Zuid 11:420 min—
Fri 23 OctDordrecht Zuid 11:42No data—
Thu 22 OctDordrecht Zuid 11:55No data—
Wed 21 OctDordrecht Zuid 11:42No data—
Tue 20 OctDordrecht Zuid 11:42No data—
Mon 19 OctDordrecht Zuid 11:420 min—
Sun 18 OctDordrecht Zuid 11:420 min—
Sat 17 OctDordrecht Zuid 11:420 min—
Fri 16 OctDordrecht Zuid 11:42No data—
Thu 15 OctDordrecht Zuid 11:42No data—
Wed 14 OctDordrecht Zuid 11:42No data—
Tue 13 OctDordrecht Zuid 11:420 min—
Mon 12 OctDordrecht Zuid 11:42No data—
Sun 11 OctDordrecht Zuid 11:420 min—
Sat 10 OctDordrecht Zuid 11:43+1 min—