Train R-net Qb 7124 Gorinchem – Dordrecht

Gorinchem 09:24 → Dordrecht 09:50 Daily 0 h 26 min · 7 stops R-net Qb

✓ Today’s run finished

Today, last fix heading to Dordrecht Stadspolders at 09:59 0 min

  1. Gorinchem09:24
  2. Boven-Hardinxveld09:29
  3. Hardinxveld-Giessendam09:33
  4. Sliedrecht09:37
  5. Sliedrecht Baanhoek09:40
  6. Dordrecht Stadspolders09:44
  7. Dordrecht09:50

Next service: tomorrow 09:24 from Gorinchem · Sat 14 Nov

Next departure 09:24 tomorrow · Gorinchem
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 2 full · 14 partial · 14 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 3 full · 17 partial · 69 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

Worst days

  • Tue 10 Nov Max en route +14 min · last fix heading to Dordrecht Stadspolders +14 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 0% · 0
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 67% T n=3
  • 100% W n=3
  • 100% T n=3
  • 100% F n=2
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 20 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
09:24on time +1 min
09:29 / 09:30— —
09:33— —
09:37— —
09:40— —
09:44 / 09:45— —
09: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
Fri 13 NovDordrecht Stadspolders 09:59Partial coverage0 min—
Thu 12 NovDordrecht Stadspolders 09:59Partial coverage0 min—
Wed 11 NovDordrecht Stadspolders 09:59Partial coverage0 min—
Tue 10 NovDordrecht Stadspolders 10:13Partial coverage+14 min+14 min
Mon 9 NovDordrecht Stadspolders 09:59Partial coverage0 min—
Sun 8 NovDordrecht Stadspolders 09:440 min—
Sat 7 NovDordrecht Stadspolders 09:59Partial coverage0 min—
Fri 6 NovDordrecht Stadspolders 10:03No data—
Thu 5 NovDordrecht Stadspolders 10:02No data—
Wed 4 NovDordrecht Stadspolders 09:59Partial coverage+1 min+1 min
Tue 3 NovDordrecht Stadspolders 10:04Partial coverage0 min—
Mon 2 NovDordrecht Stadspolders 09:59Partial coverage0 min—
Sun 1 NovDordrecht Stadspolders 09:45No data—
Sat 31 OctDordrecht Stadspolders 09:59No data—
Fri 30 OctDordrecht Stadspolders 10:00No data—
Thu 29 OctDordrecht Stadspolders 09:59Partial coverage0 min—
Wed 28 OctDordrecht Stadspolders 09:59Partial coverage0 min—
Tue 27 OctDordrecht Stadspolders 10:02No data—
Mon 26 OctDordrecht Stadspolders 10:00No data—
Sun 25 OctDordrecht Stadspolders 09:44No data—
Sat 24 OctDordrecht Stadspolders 10:00Partial coverage0 min—
Fri 23 OctDordrecht Stadspolders 09:59No data—
Thu 22 OctDordrecht Stadspolders 10:05No data—
Wed 21 OctDordrecht Stadspolders 10:00No data—
Tue 20 OctDordrecht Stadspolders 09:59No data—
Mon 19 OctDordrecht Stadspolders 10:00Partial coverage0 min—
Sun 18 OctDordrecht Stadspolders 09:45+1 min+1 min
Sat 17 OctDordrecht Stadspolders 10:00Partial coverage+1 min+2 min
Fri 16 OctDordrecht Stadspolders 10:00No data—
Thu 15 OctDordrecht Stadspolders 09:59No data—