Train R-net Qb 7181 Dordrecht – Gorinchem

Dordrecht 21:41 → Gorinchem 22:05 Daily 0 h 24 min · 7 stops R-net Qb

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 21:41 from Dordrecht · Wed 11 Nov

Next departure 21:41 today · Dordrecht
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 3 no data
On-time · 90 days
100%
6/6 runs under 3 min
RT coverage: 0 full · 6 partial · 20 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 6 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
21:41on time on time
21:44— —
21:48— —
21:51 / 21:52— —
21:56— —
21:59— —
22:05— —

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
Sun 8 NovBoven-Hardinxveld 22:14Partial coverage0 min+1 min
Sat 7 NovBoven-Hardinxveld 22:14Partial coverage+2 min+2 min
Sun 1 NovBoven-Hardinxveld 22:13Partial coverage0 min—
Sat 31 OctBoven-Hardinxveld 22:16Partial coverage0 min—
Sun 25 OctBoven-Hardinxveld 22:14No data—
Sat 24 OctBoven-Hardinxveld 22:13No data—
Sun 18 OctBoven-Hardinxveld 22:14Partial coverage+1 min+2 min
Sat 17 OctBoven-Hardinxveld 22:14No data—
Sun 11 OctBoven-Hardinxveld 22:14Partial coverage0 min+1 min
Sat 10 OctBoven-Hardinxveld 22:13No data—
Sun 4 OctBoven-Hardinxveld 22:13No data—
Sat 3 OctBoven-Hardinxveld 22:14No data—
Sun 27 SeptBoven-Hardinxveld 22:14No data—
Sat 26 SeptBoven-Hardinxveld 22:15No data—
Sun 20 SeptBoven-Hardinxveld 22:22No data—
Sat 19 SeptBoven-Hardinxveld 22:13No data—
Sun 13 SeptBoven-Hardinxveld 22:14No data—
Sat 12 SeptBoven-Hardinxveld 22:14No data—
Sun 6 SeptBoven-Hardinxveld 22:13No data—
Sat 5 SeptBoven-Hardinxveld 22:13No data—
Sun 30 AugBoven-Hardinxveld 22:14No data—
Sat 29 AugBoven-Hardinxveld 22:13No data—
Sun 23 AugBoven-Hardinxveld 22:14No data—
Sat 22 AugBoven-Hardinxveld 22:14No data—
Sun 16 AugBoven-Hardinxveld 22:14No data—
Sat 15 AugBoven-Hardinxveld 22:14No data—