Train R-net Qb 7126 Gorinchem – Dordrecht
It does not run today
Last recorded run: Saturday 14 November 0 min
Next service: tomorrow 09:54 from Gorinchem · Mon 16 Nov
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 +7 min · last fix heading to Dordrecht Stadspolders +5 min
Distribution · 90 days
19 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 95% · 18
- 3–10 min 5% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 75% T n=4
- 100% W n=3
- 100% T n=3
- 100% F n=2
- 100% S n=5
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 19 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 09:54 | on time | on time | |
| 09:59 / 10:00 | — | — | |
| 10:03 | — | — | |
| 10:07 | — | — | |
| 10:10 | — | — | |
| 10:14 / 10:15 | — | — | |
| 10: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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 14 Nov | Dordrecht Stadspolders 10:29Partial coverage | 0 min | — |
| Fri 13 Nov | Dordrecht Stadspolders 10:29Partial coverage | 0 min | — |
| Thu 12 Nov | Dordrecht Stadspolders 10:29Partial coverage | 0 min | — |
| Wed 11 Nov | Dordrecht Stadspolders 10:29Partial coverage | 0 min | — |
| Tue 10 Nov | Dordrecht Stadspolders 10:34Partial coverage | +5 min | +7 min |
| Mon 9 Nov | Dordrecht Stadspolders 10:29Partial coverage | 0 min | — |
| Sat 7 Nov | Dordrecht Stadspolders 10:29Partial coverage | 0 min | — |
| Fri 6 Nov | Dordrecht Stadspolders 10:33 | No data | — |
| Thu 5 Nov | Dordrecht Stadspolders 10:29 | No data | — |
| Wed 4 Nov | Dordrecht Stadspolders 10:29Partial coverage | 0 min | — |
| Tue 3 Nov | Dordrecht Stadspolders 10:33 | No data | — |
| Mon 2 Nov | Dordrecht Stadspolders 10:32 | No data | — |
| Sat 31 Oct | Dordrecht Stadspolders 10:29 | No data | — |
| Fri 30 Oct | Dordrecht Stadspolders 10:29 | No data | — |
| Thu 29 Oct | Dordrecht Stadspolders 10:29Partial coverage | 0 min | — |
| Wed 28 Oct | Dordrecht Stadspolders 10:29Partial coverage | 0 min | — |
| Tue 27 Oct | Dordrecht Stadspolders 10:32Partial coverage | 0 min | — |
| Mon 26 Oct | Dordrecht Stadspolders 10:29 | No data | — |
| Sat 24 Oct | Dordrecht Stadspolders 10:30Partial coverage | 0 min | — |
| Fri 23 Oct | Dordrecht Stadspolders 10:29 | No data | — |
| Thu 22 Oct | Dordrecht Stadspolders 10:33 | No data | — |
| Wed 21 Oct | Dordrecht Stadspolders 10:31 | No data | — |
| Tue 20 Oct | Dordrecht Stadspolders 10:29Partial coverage | 0 min | — |
| Mon 19 Oct | Dordrecht Stadspolders 10:29Partial coverage | 0 min | — |
| Sat 17 Oct | Dordrecht Stadspolders 10:30Partial coverage | 0 min | — |
| Fri 16 Oct | Dordrecht Stadspolders 10:29 | No data | — |
| Thu 15 Oct | Dordrecht Stadspolders 10:30 | No data | — |
| Wed 14 Oct | Dordrecht Stadspolders 10:30 | No data | — |
| Tue 13 Oct | Dordrecht Stadspolders 10:29 | No data | — |
| Mon 12 Oct | Dordrecht Stadspolders 10:32 | No data | — |