Train R-net Qb 7245 Dordrecht – Geldermalsen

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

✓ Today’s run finished

Today, last fix heading to Beesd at 13:44 No data

  1. Dordrecht12:41
  2. Sliedrecht Baanhoek12:48
  3. Sliedrecht12:51
  4. Boven-Hardinxveld12:59
  5. Arkel13:16
  6. Beesd13:30
  7. Geldermalsen13:36

Next service: tomorrow 12:41 from Dordrecht · Sat 7 Nov

Next departure 12:41 tomorrow · Dordrecht
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 3 full · 9 partial · 18 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 3 full · 12 partial · 74 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

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

  • Early 0% · 0
  • On time 100% · 15
  • 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=2
  • 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, 15 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:41on time on time
12:44— —
12:48— —
12:51 / 12:52— —
12:55— —
12:59 / 13:01— —
13:07 / 13:12— —
13:16— —
13:23 / 13:24— —
13:30— —
13:36— —

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