Train R-net Qb 7253 Dordrecht – Geldermalsen

Dordrecht 14:41 → Geldermalsen 15:36 Daily 0 h 55 min · 11 stops R-net Qb

✓ Today’s run finished

Today, last fix heading to Beesd at 15:44 0 min

  1. Dordrecht14:41
  2. Sliedrecht Baanhoek14:48
  3. Sliedrecht14:51
  4. Boven-Hardinxveld14:59
  5. Arkel15:16
  6. Beesd15:30
  7. Geldermalsen15:36

Next service: tomorrow 14:41 from Dordrecht · Sat 21 Nov

Next departure 14:41 tomorrow · Dordrecht
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 3 full · 18 partial · 9 no data
On-time · 90 days
100%
32/32 runs under 3 min
RT coverage: 5 full · 27 partial · 57 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

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

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

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=3
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 32 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
14:41on time on time
14:44≈ on time ≈ on time
14:48≈ on time ≈ on time
14:51 / 14:52≈ on time ≈ on time
14:55≈ on time ≈ on time
14:59 / 15:01≈ on time ≈ on time
15:07 / 15:12≈ on time ≈ on time
15:16≈ on time ≈ on time
15:23 / 15:24≈ on time ≈ on time
15:30≈ on time ≈ on time
15:36on time on time

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 NovBeesd 15:44Partial coverage0 min—
Thu 19 NovBeesd 15:44Partial coverage0 min—
Wed 18 NovBeesd 15:44Partial coverage0 min—
Tue 17 NovBeesd 15:44Partial coverage0 min—
Mon 16 NovBeesd 15:45Partial coverage0 min—
Sun 15 NovBeesd 15:440 min—
Sat 14 NovBeesd 15:44Partial coverage0 min—
Fri 13 NovBeesd 15:44Partial coverage0 min—
Thu 12 NovBeesd 15:44Partial coverage0 min—
Wed 11 NovBeesd 15:44Partial coverage0 min—
Tue 10 NovArkel 15:29Partial coverage0 min—
Mon 9 NovBeesd 15:45Partial coverage0 min—
Sun 8 NovBeesd 15:440 min—
Sat 7 NovBeesd 15:44Partial coverage0 min—
Fri 6 NovBeesd 15:44No data—
Thu 5 NovBeesd 15:44No data—
Wed 4 NovBeesd 15:44Partial coverage0 min—
Tue 3 NovBeesd 15:44No data—
Mon 2 NovBeesd 15:44No data—
Sun 1 NovBeesd 15:450 min—
Sat 31 OctBeesd 15:44Partial coverage0 min—
Fri 30 OctBeesd 15:45No data—
Thu 29 OctBeesd 15:45Partial coverage0 min—
Wed 28 OctBeesd 15:44Partial coverage0 min—
Tue 27 OctBeesd 15:44Partial coverage0 min—
Mon 26 OctBeesd 15:44No data—
Sun 25 OctBeesd 15:45No data—
Sat 24 OctBeesd 15:44Partial coverage0 min—
Fri 23 OctBeesd 15:45No data—
Thu 22 OctBeesd 15:44No data—