Train R-net Qb 7291 Dordrecht – Geldermalsen

Dordrecht 00:11 → Geldermalsen 00:59 Daily 0 h 48 min · 12 stops R-net Qb

It has not run yet today

Last recorded run: Sunday 11 October 0 min

Next service: tomorrow 00:11 from Dordrecht · Wed 14 Oct

Next departure 00:11 tomorrow · Dordrecht
On-time · 30 days
—
Too little data (1/4 runs with data)
RT coverage: 0 full · 1 partial · 3 no data
On-time · 90 days
—
Too little data (1/13 runs with data)
RT coverage: 0 full · 1 partial · 12 no data
Typical delay
—
Needs at least 5 runs with data (1 so far)
P90
—
Needs at least 5 runs with data (1 so far)

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

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

  • Early 0% · 0
  • On time 100% · 1
  • 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
  • — S n=0
  • 100% S n=1

Stops and timetable

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

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.

Recent runs

DateLast stopFinalMax
Sun 11 OctBeesd 01:09Partial coverage0 min—
Sun 4 OctBeesd 01:08No data—
Sun 27 SeptBeesd 01:10No data—
Sun 20 SeptBeesd 01:09No data—
Sun 13 SeptBeesd 01:10No data—
Sun 6 SeptBeesd 01:10No data—
Sun 30 AugBeesd 01:08No data—
Sun 23 AugBeesd 01:08No data—
Sun 16 AugBeesd 01:09No data—
Sun 9 AugBeesd 01:21No data—
Sun 2 AugBeesd 01:09No data—
Sun 26 JulBeesd 01:09No data—
Sun 19 JulBeesd 01:09No data—