Train R-net Qb 7265 Dordrecht – Geldermalsen

Dordrecht 17:41 → Geldermalsen 18:36 Daily 0 h 55 min · 11 stops R-net Qb

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 17:41 from Dordrecht · Fri 6 Nov

Next departure 17:41 today · Dordrecht
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 4 full · 10 partial · 15 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 4 full · 13 partial · 71 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 Geldermalsen, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
17:41on time on time
17:44— —
17:48— —
17:51 / 17:52— —
17:55— —
17:59 / 18:01— —
18:07 / 18:12— —
18:16— —
18:23 / 18:24— —
18:30— —
18:36— —

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 5 NovGorinchem 18:24No data—
Wed 4 NovGorinchem 18:24Partial coverage0 min—
Tue 3 NovGorinchem 18:24No data—
Mon 2 NovBoven-Hardinxveld 18:14No data—
Sun 1 NovBeesd 18:440 min—
Sat 31 OctBeesd 18:44Partial coverage0 min—
Fri 30 OctBeesd 18:44No data—
Thu 29 OctBoven-Hardinxveld 18:15No data—
Wed 28 OctGorinchem 18:26Partial coverage0 min—
Tue 27 OctBoven-Hardinxveld 18:15No data—
Mon 26 OctBoven-Hardinxveld 18:15Partial coverage+2 min+2 min
Sun 25 OctBeesd 18:45No data—
Sat 24 OctBeesd 18:45Partial coverage0 min—
Fri 23 OctBeesd 18:44No data—
Thu 22 OctBeesd 18:44No data—
Wed 21 OctBeesd 18:44No data—
Tue 20 OctBeesd 18:44Partial coverage0 min—
Mon 19 OctBeesd 18:44Partial coverage0 min—
Sun 18 OctBeesd 18:440 min—
Sat 17 OctBeesd 18:44No data—
Fri 16 OctBeesd 18:44No data—
Thu 15 OctBeesd 18:44No data—
Wed 14 OctBeesd 18:42No data—
Tue 13 OctBeesd 18:44No data—
Mon 12 OctBeesd 18:44Partial coverage0 min—
Sun 11 OctBeesd 18:440 min—
Sat 10 OctBeesd 18:44Partial coverage0 min—
Fri 9 OctBeesd 18:44Partial coverage0 min—
Thu 8 OctBoven-Hardinxveld 18:160 min—
Wed 7 OctBoven-Hardinxveld 18:15Partial coverage0 min—