Train R-net Qb 7279 Dordrecht – Geldermalsen

Dordrecht 21:11 → Geldermalsen 22:06 Daily 0 h 55 min · 12 stops R-net Qb

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: tomorrow 21:11 from Dordrecht · Thu 19 Nov

Next departure 21:11 tomorrow · Dordrecht
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 3 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 18 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 8 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
21:11on time on time
21:14— —
21:18— —
21:21 / 21:22— —
21:25— —
21:27— —
21:30 / 21:31— —
21:37 / 21:42— —
21:46— —
21:53 / 21:54— —
22:00— —
22:06— —

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
Sun 15 NovBeesd 22:14Partial coverage0 min—
Sat 14 NovBeesd 22:14Partial coverage0 min—
Sun 8 NovBeesd 22:14Partial coverage0 min—
Sat 7 NovBeesd 22:14Partial coverage0 min—
Sun 1 NovBeesd 22:14Partial coverage0 min—
Sat 31 OctBeesd 22:14No data—
Sun 25 OctBeesd 22:15No data—
Sat 24 OctBeesd 22:14No data—
Sun 18 OctBeesd 22:14Partial coverage0 min—
Sat 17 OctBeesd 22:14No data—
Sun 11 OctBeesd 22:14Partial coverage0 min—
Sat 10 OctBeesd 22:14Partial coverage0 min—
Sun 4 OctBeesd 22:15No data—
Sat 3 OctBeesd 22:14No data—
Sun 27 SeptBeesd 22:14No data—
Sat 26 SeptBeesd 22:15No data—
Sun 20 SeptBeesd 22:14No data—
Sat 19 SeptBeesd 22:14No data—
Sun 13 SeptBeesd 22:15No data—
Sat 12 SeptBeesd 22:15No data—
Sun 6 SeptBeesd 22:14No data—
Sat 5 SeptBeesd 22:14No data—
Sun 30 AugBeesd 22:15No data—
Sat 29 AugBeesd 22:14No data—
Sun 23 AugBeesd 22:14No data—
Sat 22 AugBeesd 22:15No data—