Train R-net Qb 7163 Dordrecht – Gorinchem

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

Running now · updated 17:54

Heading to Gorinchem 0 min

Estimated arrival at Gorinchem 17:50

  1. Dordrecht17:26
  2. Dordrecht Stadspolders17:29
  3. Sliedrecht Baanhoek17:33
  4. Sliedrecht17:36
  5. Hardinxveld-Giessendam17:41
  6. Boven-Hardinxveld17:44
  7. Gorinchem17:50

Today it is running no worse than usual: typical arrival delay is 0 min; 86% of the last 14 runs arrived on time.

Open live map ↗ Full trip card
Open live card ↗
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 0 full · 14 partial · 11 no data
On-time · 90 days
86%
12/14 runs under 3 min
RT coverage: 0 full · 14 partial · 62 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: +3 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

Worst days

  • Wed 7 Oct Max en route +5 min · last fix heading to Boven-Hardinxveld +4 min
  • Thu 8 Oct Max en route +3 min · last fix heading to Boven-Hardinxveld +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 12
  • 3–10 min 14% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

StopSched.Today
Dordrecht
17:26
Dordrecht Stadspolders
17:29
Sliedrecht Baanhoek
17:33
Sliedrecht
17:36 / 17:37
Hardinxveld-Giessendam
17:41
Boven-Hardinxveld
17:44
Gorinchem
17: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.

Recent runs

DateLast stopFinalMax
Mon 2 NovBoven-Hardinxveld 17:49Partial coverage0 min—
Sat 31 OctBoven-Hardinxveld 18:00Partial coverage+1 min+2 min
Fri 30 OctBoven-Hardinxveld 17:58No data—
Thu 29 OctBoven-Hardinxveld 17:58No data—
Wed 28 OctBoven-Hardinxveld 17:54Partial coverage0 min—
Tue 27 OctBoven-Hardinxveld 17:58Partial coverage0 min—
Mon 26 OctBoven-Hardinxveld 17:58No data—
Sat 24 OctBoven-Hardinxveld 17:59Partial coverage+2 min+2 min
Fri 23 OctBoven-Hardinxveld 18:04No data—
Thu 22 OctBoven-Hardinxveld 17:55No data—
Wed 21 OctBoven-Hardinxveld 17:58No data—
Tue 20 OctBoven-Hardinxveld 17:58Partial coverage0 min—
Mon 19 OctBoven-Hardinxveld 17:58Partial coverage0 min—
Sat 17 OctBoven-Hardinxveld 17:58No data—
Fri 16 OctBoven-Hardinxveld 18:01No data—
Thu 15 OctBoven-Hardinxveld 17:58No data—
Wed 14 OctBoven-Hardinxveld 18:03No data—
Tue 13 OctBoven-Hardinxveld 17:58No data—
Mon 12 OctBoven-Hardinxveld 17:53Partial coverage0 min—
Sat 10 OctBoven-Hardinxveld 17:59Partial coverage0 min+1 min
Fri 9 OctBoven-Hardinxveld 17:58Partial coverage+3 min+4 min
Thu 8 OctBoven-Hardinxveld 17:58Partial coverage+3 min+3 min
Wed 7 OctBoven-Hardinxveld 17:58Partial coverage+4 min+5 min
Tue 6 OctBoven-Hardinxveld 17:58Partial coverage0 min+1 min
Mon 5 OctBoven-Hardinxveld 17:58Partial coverage+3 min+3 min
Sat 3 OctBoven-Hardinxveld 17:59No data—
Fri 2 OctBoven-Hardinxveld 17:58No data—
Thu 1 OctBoven-Hardinxveld 17:58No data—
Wed 30 SeptBoven-Hardinxveld 17:58No data—
Tue 29 SeptBoven-Hardinxveld 17:53No data—