Train R-net Qb 7140 Gorinchem – Dordrecht

Gorinchem 13:24 → Dordrecht 13:50 Mon, Tue, Wed, Thu, Fri, Sat 0 h 26 min · 7 stops R-net Qb

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 13:24 from Gorinchem · Thu 5 Nov

Next departure 13:24 today · Gorinchem
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 0 full · 9 partial · 15 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 64 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 Dordrecht, 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

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

  • Early 0% · 0
  • On time 100% · 10
  • 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=2
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 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, 10 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
13:24on time on time
13:29 / 13:30— —
13:33— —
13:37— —
13:40— —
13:44 / 13:45— —
13: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 NovDordrecht Stadspolders 13:59Partial coverage0 min+1 min
Tue 3 NovDordrecht Stadspolders 13:59No data—
Mon 2 NovDordrecht Stadspolders 13:59No data—
Fri 30 OctDordrecht Stadspolders 13:59No data—
Thu 29 OctDordrecht Stadspolders 13:59No data—
Wed 28 OctDordrecht Stadspolders 14:00Partial coverage0 min—
Tue 27 OctDordrecht Stadspolders 14:00Partial coverage0 min—
Mon 26 OctDordrecht Stadspolders 14:00No data—
Sat 24 OctDordrecht Stadspolders 13:59No data—
Fri 23 OctDordrecht Stadspolders 14:00No data—
Thu 22 OctDordrecht Stadspolders 13:59No data—
Wed 21 OctDordrecht Stadspolders 14:01No data—
Tue 20 OctDordrecht Stadspolders 14:00Partial coverage0 min—
Mon 19 OctDordrecht Stadspolders 13:59Partial coverage0 min—
Sat 17 OctDordrecht Stadspolders 14:00No data—
Fri 16 OctDordrecht Stadspolders 14:00No data—
Thu 15 OctDordrecht Stadspolders 13:59No data—
Wed 14 OctDordrecht Stadspolders 13:59No data—
Tue 13 OctDordrecht Stadspolders 13:59No data—
Mon 12 OctDordrecht Stadspolders 14:00No data—
Sat 10 OctDordrecht Stadspolders 14:00Partial coverage+1 min+1 min
Fri 9 OctDordrecht Stadspolders 14:00Partial coverage+1 min+2 min
Thu 8 OctDordrecht Stadspolders 14:00Partial coverage0 min+1 min
Wed 7 OctDordrecht Stadspolders 13:59Partial coverage0 min—
Tue 6 OctDordrecht Stadspolders 13:59No data—
Mon 5 OctDordrecht Stadspolders 14:00Partial coverage+1 min—
Sat 3 OctDordrecht Stadspolders 13:59No data—
Fri 2 OctDordrecht Stadspolders 13:59No data—
Thu 1 OctDordrecht Stadspolders 13:59No data—
Wed 30 SeptDordrecht Stadspolders 14:00No data—