Train R-net Qb 7143 Dordrecht – Gorinchem

Dordrecht 12:26 → Gorinchem 12: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: Thursday 5 November No data

Next service: today 12:26 from Dordrecht · Fri 6 Nov

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

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

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

On-time by weekday

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

Stops and timetable

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

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