Train R-net Qb 7165 Dordrecht – Gorinchem

Dordrecht 17:56 → Gorinchem 18:20 Mon, Tue, Wed, Thu, Fri, Sat 0 h 24 min · 7 stops R-net Qb

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 17:56 from Dordrecht · Thu 5 Nov

Next departure 17:56 today · Dordrecht
On-time · 30 days
70%
7/10 runs under 3 min
RT coverage: 0 full · 10 partial · 15 no data
On-time · 90 days
67%
8/12 runs under 3 min
RT coverage: 0 full · 12 partial · 63 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Gorinchem, in minutes. One bar per run.

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

Worst days

  • Sat 10 Oct Max en route +5 min · last fix heading to Boven-Hardinxveld +5 min
  • Wed 7 Oct Max en route +5 min · last fix heading to Sliedrecht +5 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Boven-Hardinxveld +4 min
  • Mon 5 Oct Max en route +4 min · last fix heading to Hardinxveld-Giessendam +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 67% · 8
  • 3–10 min 33% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=3
  • 50% W n=2
  • 100% T n=1
  • 0% F n=1
  • 50% S n=2
  • — S n=0

Stops and timetable

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

Last 90 days, 12 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:56on time on time
17:59— —
18:03— —
18:06 / 18:07— —
18:11— —
18:14— —
18:20— —

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
Wed 4 NovBoven-Hardinxveld 18:28No data—
Tue 3 NovHardinxveld-Giessendam 18:24No data—
Mon 2 NovSliedrecht 18:19No data—
Sat 31 OctBoven-Hardinxveld 18:30Partial coverage+2 min+2 min
Fri 30 OctBoven-Hardinxveld 18:28No data—
Thu 29 OctDordrecht Stadspolders 18:13No data—
Wed 28 OctHardinxveld-Giessendam 18:25Partial coverage0 min—
Tue 27 OctSliedrecht Baanhoek 18:17Partial coverage0 min—
Mon 26 OctSliedrecht 18:21No data—
Sat 24 OctBoven-Hardinxveld 18:31No data—
Fri 23 OctBoven-Hardinxveld 18:28No data—
Thu 22 OctBoven-Hardinxveld 18:28No data—
Wed 21 OctBoven-Hardinxveld 18:28No data—
Tue 20 OctBoven-Hardinxveld 18:28Partial coverage0 min—
Mon 19 OctBoven-Hardinxveld 18:28Partial coverage0 min—
Sat 17 OctBoven-Hardinxveld 18:28No data—
Fri 16 OctBoven-Hardinxveld 18:30No data—
Thu 15 OctBoven-Hardinxveld 18:28No data—
Wed 14 OctBoven-Hardinxveld 18:31No data—
Tue 13 OctBoven-Hardinxveld 18:28No data—
Mon 12 OctBoven-Hardinxveld 18:28Partial coverage0 min—
Sat 10 OctBoven-Hardinxveld 18:33Partial coverage+5 min+5 min
Fri 9 OctBoven-Hardinxveld 18:23Partial coverage+4 min+4 min
Thu 8 OctSliedrecht Baanhoek 18:17Partial coverage+2 min+2 min
Wed 7 OctSliedrecht 18:21Partial coverage+5 min+5 min
Tue 6 OctSliedrecht Baanhoek 18:17Partial coverage0 min—
Mon 5 OctHardinxveld-Giessendam 18:25Partial coverage+3 min+4 min
Sat 3 OctBoven-Hardinxveld 18:29No data—
Fri 2 OctBoven-Hardinxveld 18:28No data—
Thu 1 OctSliedrecht Baanhoek 18:18No data—