Train R-net Qb 7220 Geldermalsen – Dordrecht

Geldermalsen 07:41 → Dordrecht 08:35 Mon, Tue, Wed, Thu, Fri, Sat 0 h 54 min · 11 stops R-net Qb

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 07:41 from Geldermalsen · Fri 6 Nov

Next departure 07:41 today · Geldermalsen
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 4 full · 7 partial · 14 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 5 full · 9 partial · 61 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
07:41on time +1 min
07:47≈ on time ≈ on time
07:53 / 07:54≈ on time ≈ on time
08:00≈ on time ≈ on time
08:05 / 08:08≈ on time ≈ +1 min
08:13 / 08:14≈ on time ≈ +1 min
08:18≈ on time ≈ +1 min
08:20 / 08:22≈ on time ≈ +1 min
08:25≈ on time ≈ +1 min
08:29 / 08:30≈ on time ≈ +1 min
08:35+1 min +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
Thu 5 NovDordrecht Stadspolders 08:49No data—
Wed 4 NovDordrecht Stadspolders 08:48Partial coverage+3 min+3 min
Tue 3 NovDordrecht Stadspolders 08:49No data—
Mon 2 NovDordrecht Stadspolders 08:52No data—
Sat 31 OctDordrecht Stadspolders 08:45+1 min+1 min
Fri 30 OctDordrecht Stadspolders 08:45No data—
Thu 29 OctDordrecht Stadspolders 08:46No data—
Wed 28 OctDordrecht Stadspolders 08:46Partial coverage0 min—
Tue 27 OctDordrecht Stadspolders 08:51Partial coverage0 min—
Mon 26 OctDordrecht Stadspolders 08:46No data—
Sat 24 OctDordrecht Stadspolders 08:45+1 min+2 min
Fri 23 OctDordrecht Stadspolders 08:45No data—
Thu 22 OctDordrecht Stadspolders 08:47No data—
Wed 21 OctDordrecht Stadspolders 08:45No data—
Tue 20 OctDordrecht Stadspolders 08:45Partial coverage0 min—
Mon 19 OctDordrecht Stadspolders 08:45Partial coverage0 min—
Sat 17 OctDordrecht Stadspolders 08:450 min+1 min
Fri 16 OctDordrecht Stadspolders 08:45No data—
Thu 15 OctDordrecht Stadspolders 08:45No data—
Wed 14 OctDordrecht Stadspolders 08:44No data—
Tue 13 OctDordrecht Stadspolders 08:47No data—
Mon 12 OctDordrecht Stadspolders 08:52No data—
Sat 10 OctDordrecht Stadspolders 08:450 min—
Fri 9 OctDordrecht Stadspolders 08:48Partial coverage+3 min+3 min
Thu 8 OctDordrecht Stadspolders 08:47Partial coverage+2 min+3 min
Wed 7 OctDordrecht Stadspolders 08:45Partial coverage0 min+1 min
Tue 6 OctDordrecht Stadspolders 08:47Partial coverage+2 min+3 min
Mon 5 OctDordrecht Stadspolders 08:47No data—
Sat 3 OctDordrecht Stadspolders 08:45No data—
Fri 2 OctDordrecht Stadspolders 08:45No data—