Train R-net Qb 7118 Gorinchem – Dordrecht

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

✓ Today’s run finished

Today, last fix heading to Dordrecht Stadspolders at 08:39 No data

  1. Gorinchem07:54
  2. Boven-Hardinxveld07:59
  3. Hardinxveld-Giessendam08:03
  4. Sliedrecht08:07
  5. Sliedrecht Baanhoek08:10
  6. Dordrecht Stadspolders08:14
  7. Dordrecht08:20

Next service: Monday 07:54 from Gorinchem · Mon 9 Nov

Next departure 07:54 Monday · Gorinchem
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 0 full · 8 partial · 14 no data
On-time · 90 days
90%
9/10 runs under 3 min
RT coverage: 0 full · 10 partial · 54 no data
Typical delay
0min
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 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

  • Wed 4 Nov Max en route +4 min · last fix heading to Dordrecht Stadspolders +4 min

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 90% · 9
  • 3–10 min 10% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 67% W n=3
  • 100% T n=1
  • 100% F n=1
  • — S n=0
  • — 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
07:54on time on time
07:59 / 08:00— —
08:03— —
08:07— —
08:10— —
08:14 / 08:15— —
08: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 08:39No data—
Thu 5 NovDordrecht Stadspolders 08:33No data—
Wed 4 NovDordrecht Stadspolders 08:34Partial coverage+4 min+4 min
Tue 3 NovDordrecht Stadspolders 08:34No data—
Mon 2 NovDordrecht Stadspolders 08:29No data—
Fri 30 OctDordrecht Stadspolders 08:30No data—
Thu 29 OctDordrecht Stadspolders 08:31No data—
Wed 28 OctDordrecht Stadspolders 08:31Partial coverage0 min—
Tue 27 OctDordrecht Stadspolders 08:35Partial coverage0 min—
Mon 26 OctDordrecht Stadspolders 08:31Partial coverage0 min—
Fri 23 OctDordrecht Stadspolders 08:30No data—
Thu 22 OctDordrecht Stadspolders 08:32No data—
Wed 21 OctDordrecht Stadspolders 08:31No data—
Tue 20 OctDordrecht Stadspolders 08:29Partial coverage0 min—
Mon 19 OctDordrecht Stadspolders 08:31Partial coverage0 min—
Fri 16 OctDordrecht Stadspolders 08:30No data—
Thu 15 OctDordrecht Stadspolders 08:31No data—
Wed 14 OctDordrecht Stadspolders 08:30No data—
Tue 13 OctDordrecht Stadspolders 08:33No data—
Mon 12 OctDordrecht Stadspolders 08:37No data—
Fri 9 OctDordrecht Stadspolders 08:29Partial coverage0 min—
Thu 8 OctDordrecht Stadspolders 08:32Partial coverage+1 min+3 min
Wed 7 OctDordrecht Stadspolders 08:31Partial coverage+1 min+2 min
Tue 6 OctDordrecht Stadspolders 08:31Partial coverage+1 min+3 min
Mon 5 OctDordrecht Stadspolders 08:31No data—
Fri 2 OctDordrecht Stadspolders 08:30No data—
Thu 1 OctDordrecht Stadspolders 08:33No data—
Wed 30 SeptDordrecht Stadspolders 08:31No data—
Tue 29 SeptDordrecht Stadspolders 08:32No data—
Mon 28 SeptDordrecht Stadspolders 08:34No data—