Train R-net Qb 7224 Geldermalsen – Dordrecht

Geldermalsen 08:41 → Dordrecht 09:35 Mon, Tue, Wed, Thu, Fri, Sat 0 h 54 min · 11 stops R-net Qb

✓ Today’s run finished

Today, last fix heading to Dordrecht Stadspolders at 09:44 0 min

  1. Geldermalsen08:41
  2. Leerdam08:53
  3. Arkel09:00
  4. Boven-Hardinxveld09:13
  5. Sliedrecht09:20
  6. Dordrecht Stadspolders09:29
  7. Dordrecht09:35

Next service: tomorrow 08:41 from Geldermalsen · Tue 10 Nov

Next departure 08:41 tomorrow · Geldermalsen
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 15 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 0 full · 14 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Dordrecht, 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

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

  • Early 0% · 0
  • On time 100% · 14
  • 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=2
  • 100% W n=2
  • 100% T n=2
  • 100% F n=1
  • 100% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 14 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
08:41on time on time
08:47— —
08:53 / 08:54— —
09:00— —
09:05 / 09:08— —
09:13 / 09:14— —
09:18— —
09:20 / 09:22— —
09:25— —
09:29 / 09:30— —
09:35— —

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 NovDordrecht Stadspolders 09:44Partial coverage0 min—
Sat 7 NovDordrecht Stadspolders 09:44Partial coverage0 min—
Fri 6 NovDordrecht Stadspolders 09:49No data—
Thu 5 NovDordrecht Stadspolders 09:47No data—
Wed 4 NovDordrecht Stadspolders 09:44Partial coverage+1 min+3 min
Tue 3 NovDordrecht Stadspolders 09:49Partial coverage0 min—
Mon 2 NovDordrecht Stadspolders 09:49Partial coverage0 min—
Sat 31 OctDordrecht Stadspolders 09:44No data—
Fri 30 OctDordrecht Stadspolders 09:45No data—
Thu 29 OctDordrecht Stadspolders 09:44Partial coverage0 min—
Wed 28 OctDordrecht Stadspolders 09:44Partial coverage0 min—
Tue 27 OctDordrecht Stadspolders 09:48No data—
Mon 26 OctDordrecht Stadspolders 09:45No data—
Sat 24 OctDordrecht Stadspolders 09:44Partial coverage0 min—
Fri 23 OctDordrecht Stadspolders 09:44No data—
Thu 22 OctDordrecht Stadspolders 09:50No data—
Wed 21 OctDordrecht Stadspolders 09:45No data—
Tue 20 OctDordrecht Stadspolders 09:44No data—
Mon 19 OctDordrecht Stadspolders 09:44Partial coverage0 min—
Sat 17 OctDordrecht Stadspolders 09:45Partial coverage0 min+1 min
Fri 16 OctDordrecht Stadspolders 09:44No data—
Thu 15 OctDordrecht Stadspolders 09:44No data—
Wed 14 OctDordrecht Stadspolders 09:45No data—
Tue 13 OctDordrecht Stadspolders 09:45No data—
Mon 12 OctDordrecht Stadspolders 09:52No data—
Sat 10 OctDordrecht Stadspolders 09:45Partial coverage+1 min—
Fri 9 OctDordrecht Stadspolders 09:48Partial coverage+1 min+3 min
Thu 8 OctDordrecht Stadspolders 09:45Partial coverage0 min+1 min
Wed 7 OctDordrecht Stadspolders 09:44No data—
Tue 6 OctDordrecht Stadspolders 09:45Partial coverage0 min+1 min