Train R-net Qb 7238 Geldermalsen – Dordrecht

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

✓ Today’s run finished

Today, last fix heading to Dordrecht Stadspolders at 13:14 No data

  1. Geldermalsen12:11
  2. Leerdam12:23
  3. Arkel12:30
  4. Boven-Hardinxveld12:43
  5. Sliedrecht12:50
  6. Dordrecht Stadspolders12:59
  7. Dordrecht13:05

Next service: tomorrow 12:11 from Geldermalsen · Fri 6 Nov

Next departure 12:11 tomorrow · Geldermalsen
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 3 full · 11 partial · 16 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 3 full · 13 partial · 73 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 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 (11 stops).

Last 90 days, 16 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
12:11on time on time
12:16— —
12:23 / 12:24— —
12:30— —
12:35 / 12:38— —
12:43 / 12:44— —
12:48— —
12:50 / 12:52— —
12:55— —
12:59 / 13:00— —
13: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
Thu 5 NovDordrecht Stadspolders 13:14No data—
Wed 4 NovDordrecht Stadspolders 13:14Partial coverage0 min—
Tue 3 NovDordrecht Stadspolders 13:14No data—
Mon 2 NovDordrecht Stadspolders 13:14No data—
Sun 1 NovDordrecht Stadspolders 13:160 min—
Sat 31 OctDordrecht Stadspolders 13:14Partial coverage0 min—
Fri 30 OctDordrecht Stadspolders 13:15No data—
Thu 29 OctDordrecht Stadspolders 13:15No data—
Wed 28 OctDordrecht Stadspolders 13:15Partial coverage0 min—
Tue 27 OctDordrecht Stadspolders 13:14Partial coverage0 min—
Mon 26 OctDordrecht Stadspolders 13:14No data—
Sun 25 OctDordrecht Stadspolders 13:15No data—
Sat 24 OctDordrecht Stadspolders 13:15Partial coverage0 min—
Fri 23 OctDordrecht Stadspolders 13:15No data—
Thu 22 OctDordrecht Stadspolders 13:14No data—
Wed 21 OctDordrecht Stadspolders 13:14No data—
Tue 20 OctDordrecht Stadspolders 13:14Partial coverage0 min—
Mon 19 OctDordrecht Stadspolders 13:14Partial coverage0 min—
Sun 18 OctDordrecht Stadspolders 13:150 min+1 min
Sat 17 OctDordrecht Stadspolders 13:16No data—
Fri 16 OctDordrecht Stadspolders 13:14No data—
Thu 15 OctDordrecht Stadspolders 13:26No data—
Wed 14 OctDordrecht Stadspolders 13:15No data—
Tue 13 OctDordrecht Stadspolders 13:15No data—
Mon 12 OctDordrecht Stadspolders 13:15No data—
Sun 11 OctDordrecht Stadspolders 13:140 min—
Sat 10 OctDordrecht Stadspolders 13:15Partial coverage0 min—
Fri 9 OctDordrecht Stadspolders 13:15Partial coverage0 min—
Thu 8 OctDordrecht Stadspolders 13:14Partial coverage0 min—
Wed 7 OctDordrecht Stadspolders 13:14Partial coverage0 min—