Train R-net Qb 7252 Geldermalsen – Dordrecht
It has not run yet today
Last recorded run: Sunday 8 November 0 min
Next service: today 15:41 from Geldermalsen · Mon 9 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
- Wed 7 Oct Max en route +8 min · last fix heading to Dordrecht Stadspolders +6 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 17
- 3–10 min 6% · 1
- 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
- 100% T n=2
- 100% F n=1
- 100% S n=3
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 18 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 |
|---|---|---|---|
| 15:41 | on time | +1 min | |
| 15:47 | ≈ on time | ≈ +1 min | |
| 15:53 / 15:54 | ≈ on time | ≈ +1 min | |
| 16:00 | ≈ on time | ≈ +1 min | |
| 16:05 / 16:08 | ≈ on time | ≈ +1 min | |
| 16:13 / 16:14 | ≈ on time | ≈ +1 min | |
| 16:17 | ≈ on time | ≈ +1 min | |
| 16:19 | ≈ on time | ≈ +1 min | |
| 16:22 | ≈ on time | ≈ +1 min | |
| 16:25 | ≈ on time | ≈ +1 min | |
| 16:29 / 16:30 | ≈ on time | ≈ +2 min | |
| 16:35 | on time | +2 min |
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 |
|---|---|---|---|
| Sun 8 Nov | Dordrecht Stadspolders 16:45Partial coverage | 0 min | — |
| Sat 7 Nov | Dordrecht Stadspolders 16:44 | 0 min | +1 min |
| Fri 6 Nov | Dordrecht Stadspolders 16:44 | No data | — |
| Thu 5 Nov | Dordrecht Stadspolders 16:47 | No data | — |
| Wed 4 Nov | Dordrecht Stadspolders 16:47 | No data | — |
| Tue 3 Nov | Dordrecht Stadspolders 16:44 | 0 min | — |
| Mon 2 Nov | Dordrecht Stadspolders 16:44 | 0 min | — |
| Sun 1 Nov | Dordrecht Stadspolders 16:44 | No data | — |
| Sat 31 Oct | Dordrecht Stadspolders 16:45 | 0 min | +2 min |
| Fri 30 Oct | Dordrecht Stadspolders 16:45 | No data | — |
| Thu 29 Oct | Dordrecht Stadspolders 16:45 | 0 min | — |
| Wed 28 Oct | Dordrecht Stadspolders 16:45 | 0 min | — |
| Tue 27 Oct | Dordrecht Stadspolders 16:50 | No data | — |
| Mon 26 Oct | Dordrecht Stadspolders 16:52 | No data | — |
| Sun 25 Oct | Dordrecht Stadspolders 16:48 | No data | — |
| Sat 24 Oct | Dordrecht Stadspolders 16:44 | 0 min | — |
| Fri 23 Oct | Dordrecht Stadspolders 16:49 | No data | — |
| Thu 22 Oct | Dordrecht Stadspolders 16:45 | No data | — |
| Wed 21 Oct | Dordrecht Stadspolders 16:46 | No data | — |
| Tue 20 Oct | Dordrecht Stadspolders 16:47 | 0 min | — |
| Mon 19 Oct | Dordrecht Stadspolders 16:45 | 0 min | — |
| Sun 18 Oct | Dordrecht Stadspolders 16:45Partial coverage | 0 min | — |
| Sat 17 Oct | Dordrecht Stadspolders 16:45 | No data | — |
| Fri 16 Oct | Dordrecht Stadspolders 16:45 | No data | — |
| Thu 15 Oct | Dordrecht Stadspolders 16:44 | No data | — |
| Wed 14 Oct | Dordrecht Stadspolders 16:44 | No data | — |
| Tue 13 Oct | Dordrecht Stadspolders 16:46 | No data | — |
| Mon 12 Oct | Dordrecht Stadspolders 16:47 | +2 min | +3 min |
| Sun 11 Oct | Dordrecht Stadspolders 16:45Partial coverage | 0 min | +1 min |
| Sat 10 Oct | Dordrecht Stadspolders 16:44 | No data | — |