Train R-net Qb 7264 Geldermalsen – Dordrecht

Geldermalsen 18:41 → Dordrecht 19:35 Daily 0 h 54 min · 11 stops R-net Qb

Running now · updated 19:23

Position estimated from the timetable

Heading to Dordrecht 0 min

Estimated arrival at Dordrecht 19:35

  1. Geldermalsen18:41
  2. Leerdam18:53
  3. Arkel19:00
  4. Boven-Hardinxveld19:13
  5. Sliedrecht19:20
  6. Sliedrecht Baanhoek19:25
  7. Dordrecht19:35

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 11 runs arrived on time.

On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 6 full · 5 partial · 4 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 9 full · 8 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 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

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

  • Early 0% · 0
  • On time 100% · 17
  • 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=1
  • 100% W n=1
  • — T n=0
  • 100% F n=4
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 17 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 10Today
18:41on time on time
18:47≈ on time ≈ on time
18:53 / 18:54≈ on time ≈ on time
19:00≈ on time ≈ on time
19:05 / 19:08≈ on time ≈ +1 min
19:13 / 19:14≈ on time ≈ +1 min
19:18≈ on time ≈ +1 min
19:20 / 19:22≈ on time ≈ +1 min
19:25≈ on time ≈ +1 min
19:29 / 19:30≈ on time ≈ +1 min
19:35on time +1 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

DateLast stopFinalMax
Fri 20 NovBoven-Hardinxveld 19:19Partial coverage0 min—
Wed 18 NovGeldermalsen 18:53Partial coverage0 min—
Sun 15 NovDordrecht Stadspolders 19:44+1 min+2 min
Sat 14 NovDordrecht Stadspolders 19:440 min—
Fri 13 NovLeerdam 19:08Partial coverage0 min—
Sun 8 NovDordrecht Stadspolders 19:440 min—
Sat 7 NovDordrecht Stadspolders 19:440 min—
Fri 6 NovBeesd 18:59Partial coverage0 min—
Sun 1 NovDordrecht Stadspolders 19:440 min—
Sat 31 OctDordrecht Stadspolders 19:47+2 min+2 min
Fri 30 OctLeerdam 19:08No data—
Sun 25 OctDordrecht Stadspolders 19:45No data—
Sat 24 OctDordrecht Stadspolders 19:46No data—
Fri 23 OctSliedrecht Baanhoek 19:39Partial coverage+2 min+5 min
Thu 22 OctGeldermalsen 18:55No data—
Tue 20 OctGeldermalsen 18:50Partial coverage0 min—
Mon 19 OctGeldermalsen 18:55Partial coverage0 min—
Sun 18 OctDordrecht Stadspolders 19:440 min—
Sat 17 OctDordrecht Stadspolders 19:44No data—
Fri 16 OctDordrecht Stadspolders 19:44No data—
Wed 14 OctDordrecht Stadspolders 19:42No data—
Mon 12 OctGeldermalsen 18:55Partial coverage0 min—
Sun 11 OctDordrecht Stadspolders 19:440 min—
Sat 10 OctDordrecht Stadspolders 19:45+1 min+2 min
Sun 4 OctDordrecht Stadspolders 19:45No data—
Sat 3 OctDordrecht Stadspolders 19:45No data—
Fri 2 OctBeesd 19:01No data—
Sun 27 SeptDordrecht Stadspolders 19:44No data—
Sat 26 SeptDordrecht Stadspolders 19:44No data—
Sun 20 SeptDordrecht Stadspolders 19:45No data—