Train R-net Qb 7167 Dordrecht – Gorinchem

Dordrecht 18:26 → Gorinchem 18:50 Mon, Tue, Wed, Thu, Fri 0 h 24 min · 7 stops R-net Qb

It does not run today

Last recorded run: Friday 13 November +1 min

Next service: Monday 18:26 from Dordrecht · Mon 16 Nov

Next departure 18:26 Monday · Dordrecht
On-time · 30 days
80%
4/5 runs under 3 min
RT coverage: 0 full · 5 partial · 4 no data
On-time · 90 days
71%
5/7 runs under 3 min
RT coverage: 0 full · 7 partial · 22 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Fri 23 Oct Max en route +5 min · last fix heading to Boven-Hardinxveld +5 min
  • Fri 9 Oct Max en route +3 min · last fix heading to Sliedrecht Baanhoek +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 71% · 5
  • 3–10 min 29% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 7 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
18:26on time +2 min
18:29— —
18:33— —
18:36 / 18:37— —
18:41— —
18:44— —
18:50— —

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
Fri 13 NovBoven-Hardinxveld 18:58Partial coverage+1 min+2 min
Fri 6 NovBoven-Hardinxveld 18:58Partial coverage+2 min+2 min
Fri 30 OctBoven-Hardinxveld 18:58No data—
Fri 23 OctBoven-Hardinxveld 18:53Partial coverage+5 min+5 min
Thu 22 OctBoven-Hardinxveld 18:58No data—
Wed 21 OctSliedrecht 18:51No data—
Tue 20 OctBoven-Hardinxveld 18:50Partial coverage0 min—
Mon 19 OctHardinxveld-Giessendam 18:55Partial coverage0 min—
Fri 16 OctBoven-Hardinxveld 18:58No data—
Thu 15 OctDordrecht Stadspolders 18:43No data—
Wed 14 OctBoven-Hardinxveld 18:58No data—
Tue 13 OctSliedrecht 18:50No data—
Mon 12 OctBoven-Hardinxveld 18:58Partial coverage0 min—
Fri 9 OctSliedrecht Baanhoek 18:47Partial coverage+3 min+3 min
Fri 2 OctBoven-Hardinxveld 18:58No data—
Fri 25 SeptSliedrecht Baanhoek 18:47No data—
Fri 18 SeptBoven-Hardinxveld 18:58No data—
Fri 11 SeptBoven-Hardinxveld 18:58No data—
Fri 4 SeptBoven-Hardinxveld 18:58No data—
Fri 28 AugBoven-Hardinxveld 18:54No data—
Thu 27 AugBoven-Hardinxveld 18:58No data—
Wed 26 AugBoven-Hardinxveld 18:56No data—
Tue 25 AugBoven-Hardinxveld 18:58No data—
Mon 24 AugDordrecht 18:40No data—
Fri 21 AugBoven-Hardinxveld 18:59No data—
Thu 20 AugBoven-Hardinxveld 18:55No data—
Wed 19 AugBoven-Hardinxveld 18:58No data—
Tue 18 AugBoven-Hardinxveld 18:58No data—
Mon 17 AugBoven-Hardinxveld 18:58No data—