Train R-net Qb 7154 Gorinchem – Dordrecht

Gorinchem 16:54 → Dordrecht 17:20 Mon, Tue, Wed, Thu, Fri, Sat 0 h 26 min · 7 stops R-net Qb

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 16:54 from Gorinchem · Sat 7 Nov

Next departure 16:54 today · Gorinchem
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 17 no data
On-time · 90 days
91%
10/11 runs under 3 min
RT coverage: 0 full · 11 partial · 65 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Dordrecht, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 8 Oct Max en route +4 min · last fix heading to Dordrecht Stadspolders +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 10
  • 3–10 min 9% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 11 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
16:54on time +1 min
16:59 / 17:00— —
17:03— —
17:07— —
17:10— —
17:14 / 17:15— —
17:20— —

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 6 NovDordrecht Stadspolders 17:29Partial coverage0 min—
Thu 5 NovDordrecht Stadspolders 17:29No data—
Wed 4 NovDordrecht Stadspolders 17:29No data—
Tue 3 NovDordrecht Stadspolders 17:29No data—
Mon 2 NovDordrecht Stadspolders 17:29No data—
Sat 31 OctDordrecht Stadspolders 17:30Partial coverage0 min+1 min
Fri 30 OctDordrecht Stadspolders 17:29No data—
Thu 29 OctDordrecht Stadspolders 17:29No data—
Wed 28 OctDordrecht Stadspolders 17:29Partial coverage0 min—
Tue 27 OctDordrecht Stadspolders 17:29Partial coverage0 min—
Mon 26 OctDordrecht Stadspolders 17:29No data—
Sat 24 OctDordrecht Stadspolders 17:29No data—
Fri 23 OctDordrecht Stadspolders 17:34No data—
Thu 22 OctDordrecht Stadspolders 17:32No data—
Wed 21 OctDordrecht Stadspolders 17:31No data—
Tue 20 OctDordrecht Stadspolders 17:31Partial coverage0 min—
Mon 19 OctDordrecht Stadspolders 17:31Partial coverage0 min—
Sat 17 OctDordrecht Stadspolders 17:29No data—
Fri 16 OctDordrecht Stadspolders 17:32No data—
Thu 15 OctDordrecht Stadspolders 17:29No data—
Wed 14 OctDordrecht Stadspolders 17:32No data—
Tue 13 OctDordrecht Stadspolders 17:31No data—
Mon 12 OctDordrecht Stadspolders 17:30Partial coverage0 min—
Sat 10 OctDordrecht Stadspolders 17:30No data—
Fri 9 OctDordrecht Stadspolders 17:31Partial coverage+1 min+3 min
Thu 8 OctDordrecht Stadspolders 17:29Partial coverage+4 min+4 min
Wed 7 OctDordrecht Stadspolders 17:29Partial coverage+2 min+3 min
Tue 6 OctDordrecht Stadspolders 17:29No data—
Mon 5 OctDordrecht Stadspolders 17:27Partial coverage+3 min+3 min
Sat 3 OctDordrecht Stadspolders 17:29No data—