Train R-net Qb 7266 Geldermalsen – Dordrecht

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

It has not run yet today

Last recorded run: Sunday 1 November +1 min

Next service: today 19:11 from Geldermalsen · Thu 5 Nov

Next departure 19:11 today · Geldermalsen
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 6 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 35 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 Dordrecht, 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

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

  • Early 0% · 0
  • On time 100% · 5
  • 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=2
  • 100% S n=2

Stops and timetable

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

Last 90 days, 5 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:16— —
19:23 / 19:24— —
19:30— —
19:35 / 19:38— —
19:43 / 19:44— —
19:47— —
19:49— —
19:52— —
19:55— —
19:59 / 20:00— —
20:05— —

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 1 NovDordrecht Stadspolders 20:14Partial coverage+1 min+2 min
Sat 31 OctDordrecht Stadspolders 20:14Partial coverage0 min—
Sun 25 OctDordrecht Stadspolders 20:14No data—
Sat 24 OctDordrecht Stadspolders 20:15No data—
Fri 23 OctLeerdam 19:38Partial coverage0 min—
Sun 18 OctDordrecht Stadspolders 20:14No data—
Sat 17 OctDordrecht Stadspolders 20:15No data—
Fri 16 OctSliedrecht Baanhoek 20:09No data—
Wed 14 OctHardinxveld-Giessendam 20:01No data—
Sun 11 OctDordrecht Stadspolders 20:15Partial coverage0 min—
Sat 10 OctDordrecht Stadspolders 20:14Partial coverage0 min—
Sun 4 OctDordrecht Stadspolders 20:16No data—
Sat 3 OctDordrecht Stadspolders 20:17No data—
Sun 27 SeptDordrecht Stadspolders 20:15No data—
Sat 26 SeptDordrecht Stadspolders 20:14No data—
Sun 20 SeptDordrecht Stadspolders 20:15No data—
Sat 19 SeptDordrecht Stadspolders 20:15No data—
Sun 13 SeptDordrecht Stadspolders 20:15No data—
Sat 12 SeptDordrecht Stadspolders 20:15No data—
Sun 6 SeptDordrecht Stadspolders 20:14No data—
Sat 5 SeptDordrecht Stadspolders 20:15No data—
Sun 30 AugDordrecht Stadspolders 20:14No data—
Sat 29 AugDordrecht Stadspolders 20:15No data—
Fri 28 AugArkel 19:44No data—
Sun 23 AugDordrecht Stadspolders 20:16No data—
Sat 22 AugDordrecht Stadspolders 20:15No data—
Fri 21 AugDordrecht Stadspolders 20:14No data—
Thu 20 AugGeldermalsen 19:25No data—
Wed 19 AugLeerdam 19:38No data—
Tue 18 AugBeesd 19:30No data—