Train R-net Qb 7271 Dordrecht – Geldermalsen

Dordrecht 19:11 → Geldermalsen 20:06 Daily 0 h 55 min · 12 stops R-net Qb

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: tomorrow 19:11 from Dordrecht · Thu 12 Nov

Next departure 19:11 tomorrow · Dordrecht
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 0 full · 6 partial · 5 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Geldermalsen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 8
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 8 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
19:11on time on time
19:14— —
19:18— —
19:21 / 19:22— —
19:25— —
19:27— —
19:30 / 19:31— —
19:37 / 19:42— —
19:46— —
19:53 / 19:54— —
20:00— —
20:06— —

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
Sun 8 NovBeesd 20:14Partial coverage0 min—
Sat 7 NovBeesd 20:14Partial coverage+1 min—
Sun 1 NovBeesd 20:14Partial coverage0 min—
Sat 31 OctBeesd 20:14Partial coverage0 min—
Sun 25 OctBeesd 20:15No data—
Sat 24 OctBeesd 20:14No data—
Fri 23 OctHardinxveld-Giessendam 19:41Partial coverage0 min—
Sun 18 OctBeesd 20:14Partial coverage0 min—
Sat 17 OctBeesd 20:14No data—
Fri 16 OctLeerdam 20:08No data—
Wed 14 OctArkel 20:00No data—
Sun 11 OctBeesd 20:14Partial coverage0 min—
Sat 10 OctBeesd 20:14Partial coverage0 min—
Sun 4 OctBeesd 20:16No data—
Sat 3 OctBeesd 20:15No data—
Sun 27 SeptBeesd 20:15No data—
Sat 26 SeptBeesd 20:15No data—
Sun 20 SeptBeesd 20:14No data—
Sat 19 SeptBeesd 20:14No data—
Sun 13 SeptBeesd 20:15No data—
Sat 12 SeptBeesd 20:15No data—
Sun 6 SeptBeesd 20:14No data—
Sat 5 SeptBeesd 20:14No data—
Sun 30 AugBeesd 20:15No data—
Sat 29 AugBeesd 20:14No data—
Fri 28 AugHardinxveld-Giessendam 19:41No data—
Sun 23 AugBeesd 20:14No data—
Sat 22 AugBeesd 20:14No data—
Fri 21 AugBeesd 20:14No data—
Thu 20 AugDordrecht 19:25No data—