Train R-net Qb 7151 Dordrecht – Gorinchem

Dordrecht 14:26 → Gorinchem 14:50 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 +2 min

Next service: today 14:26 from Dordrecht · Thu 5 Nov

Next departure 14:26 today · Dordrecht
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 0 full · 10 partial · 15 no data
On-time · 90 days
92%
11/12 runs under 3 min
RT coverage: 0 full · 12 partial · 63 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Wed 7 Oct Max en route +10 min · last fix heading to Boven-Hardinxveld +9 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 92% · 11
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 67% W n=3
  • 100% T n=1
  • 100% F n=1
  • 100% 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
14:26on time on time
14:29— —
14:33— —
14:36 / 14:37— —
14:41— —
14:44— —
14: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
Wed 4 NovBoven-Hardinxveld 14:59Partial coverage+2 min+3 min
Tue 3 NovBoven-Hardinxveld 14:59No data—
Mon 2 NovBoven-Hardinxveld 14:59No data—
Sat 31 OctBoven-Hardinxveld 14:59Partial coverage+1 min—
Fri 30 OctBoven-Hardinxveld 14:59No data—
Thu 29 OctBoven-Hardinxveld 14:58No data—
Wed 28 OctBoven-Hardinxveld 15:00Partial coverage0 min—
Tue 27 OctBoven-Hardinxveld 15:01Partial coverage0 min—
Mon 26 OctBoven-Hardinxveld 14:59No data—
Sat 24 OctBoven-Hardinxveld 14:59Partial coverage0 min+1 min
Fri 23 OctBoven-Hardinxveld 15:00No data—
Thu 22 OctBoven-Hardinxveld 14:59No data—
Wed 21 OctBoven-Hardinxveld 15:00No data—
Tue 20 OctBoven-Hardinxveld 15:00Partial coverage0 min—
Mon 19 OctBoven-Hardinxveld 14:58Partial coverage0 min—
Sat 17 OctBoven-Hardinxveld 15:01No data—
Fri 16 OctBoven-Hardinxveld 14:58No data—
Thu 15 OctBoven-Hardinxveld 14:58No data—
Wed 14 OctBoven-Hardinxveld 14:59No data—
Tue 13 OctBoven-Hardinxveld 15:00No data—
Mon 12 OctBoven-Hardinxveld 15:00No data—
Sat 10 OctBoven-Hardinxveld 14:58No data—
Fri 9 OctBoven-Hardinxveld 15:01Partial coverage+2 min+3 min
Thu 8 OctBoven-Hardinxveld 14:59Partial coverage0 min+1 min
Wed 7 OctBoven-Hardinxveld 15:08Partial coverage+9 min+10 min
Tue 6 OctBoven-Hardinxveld 14:59Partial coverage+1 min—
Mon 5 OctBoven-Hardinxveld 14:59Partial coverage0 min+1 min
Sat 3 OctBoven-Hardinxveld 14:58No data—
Fri 2 OctBoven-Hardinxveld 14:59No data—
Thu 1 OctBoven-Hardinxveld 14:59No data—