Train R-net Qb 7267 Dordrecht – Geldermalsen

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

It has not run yet today

Last recorded run: Friday 6 November +2 min

Next service: today 18:11 from Dordrecht · Sat 7 Nov

Next departure 18:11 today · Dordrecht
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 4 full · 8 partial · 13 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 4 full · 9 partial · 55 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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
18:11on time on time
18:14— —
18:18— —
18:21 / 18:22— —
18:25— —
18:29 / 18:31— —
18:37 / 18:42— —
18:46— —
18:53 / 18:54— —
19:00— —
19: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
Fri 6 NovArkel 18:59Partial coverage+2 min+2 min
Thu 5 NovDordrecht 18:24No data—
Wed 4 NovDordrecht Stadspolders 18:28Partial coverage0 min—
Tue 3 NovDordrecht 18:24No data—
Sun 1 NovBeesd 19:140 min—
Sat 31 OctBeesd 19:150 min—
Fri 30 OctLeerdam 19:08No data—
Wed 28 OctDordrecht 18:25Partial coverage0 min—
Sun 25 OctBeesd 19:16No data—
Sat 24 OctBeesd 19:15No data—
Fri 23 OctBeesd 19:14Partial coverage0 min—
Thu 22 OctGorinchem 18:56No data—
Wed 21 OctBoven-Hardinxveld 18:45No data—
Tue 20 OctArkel 18:50Partial coverage0 min—
Mon 19 OctGorinchem 18:56Partial coverage0 min—
Sun 18 OctBeesd 19:14No data—
Sat 17 OctBeesd 19:14No data—
Fri 16 OctBeesd 19:14No data—
Thu 15 OctHardinxveld Blauwe Zoom 18:39No data—
Wed 14 OctBeesd 19:09No data—
Tue 13 OctBoven-Hardinxveld 18:45No data—
Mon 12 OctGorinchem 18:56Partial coverage0 min—
Sun 11 OctBeesd 19:140 min—
Sat 10 OctBeesd 19:140 min—
Fri 9 OctBoven-Hardinxveld 18:45Partial coverage0 min—
Mon 5 OctDordrecht 18:25Partial coverage0 min—
Sun 4 OctBeesd 19:14No data—
Sat 3 OctBeesd 19:15No data—
Fri 2 OctArkel 19:00No data—
Sun 27 SeptBeesd 19:14No data—