Train R-net Qb 7123 Dordrecht – Gorinchem

Dordrecht 07:26 → Gorinchem 07:50 Mon, Tue, Wed, Thu, Fri 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 07:26 from Dordrecht · Thu 5 Nov

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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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
07:26on time on time
07:29— —
07:33— —
07:36 / 07:37— —
07:41— —
07:44— —
07: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 07:59Partial coverage+2 min+3 min
Tue 3 NovBoven-Hardinxveld 08:03No data—
Mon 2 NovBoven-Hardinxveld 07:58No data—
Fri 30 OctBoven-Hardinxveld 07:59Partial coverage+1 min—
Thu 29 OctBoven-Hardinxveld 07:58Partial coverage0 min—
Wed 28 OctBoven-Hardinxveld 07:59Partial coverage0 min—
Tue 27 OctBoven-Hardinxveld 08:03Partial coverage0 min—
Mon 26 OctBoven-Hardinxveld 08:00Partial coverage+1 min+2 min
Fri 23 OctBoven-Hardinxveld 08:00Partial coverage+2 min+2 min
Thu 22 OctBoven-Hardinxveld 08:00No data—
Wed 21 OctBoven-Hardinxveld 08:00No data—
Tue 20 OctBoven-Hardinxveld 07:59Partial coverage0 min—
Mon 19 OctBoven-Hardinxveld 08:00Partial coverage0 min—
Fri 16 OctBoven-Hardinxveld 08:00No data—
Thu 15 OctBoven-Hardinxveld 07:59No data—
Wed 14 OctBoven-Hardinxveld 07:59No data—
Tue 13 OctBoven-Hardinxveld 08:00No data—
Mon 12 OctBoven-Hardinxveld 08:03No data—
Fri 9 OctBoven-Hardinxveld 07:59Partial coverage0 min—
Thu 8 OctBoven-Hardinxveld 08:00Partial coverage+1 min+2 min
Wed 7 OctBoven-Hardinxveld 08:00Partial coverage+2 min+2 min
Tue 6 OctBoven-Hardinxveld 08:00Partial coverage+2 min+2 min
Mon 5 OctBoven-Hardinxveld 07:59No data—
Fri 2 OctBoven-Hardinxveld 07:58No data—
Thu 1 OctBoven-Hardinxveld 08:00No data—
Wed 30 SeptBoven-Hardinxveld 08:00No data—
Tue 29 SeptBoven-Hardinxveld 08:00No data—
Mon 28 SeptBoven-Hardinxveld 08:02No data—
Fri 25 SeptBoven-Hardinxveld 08:01No data—
Thu 24 SeptBoven-Hardinxveld 07:59No data—