Train R-net Qb 7274 Geldermalsen – Dordrecht

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

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 21:11 from Geldermalsen · Mon 9 Nov

Next departure 21:11 today · Geldermalsen
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 0 full · 4 partial · 4 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 20 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

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

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

  • Early 0% · 0
  • On time 100% · 5
  • 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=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 5 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:16— —
21:23 / 21:24— —
21:30— —
21:35 / 21:38— —
21:43 / 21:44— —
21:47— —
21:49— —
21:52— —
21:55— —
21:59 / 22:00— —
22:05— —

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 8 NovDordrecht Stadspolders 22:14Partial coverage0 min+1 min
Sat 7 NovDordrecht Stadspolders 22:14Partial coverage0 min—
Sun 1 NovDordrecht Stadspolders 22:14Partial coverage0 min+2 min
Sat 31 OctDordrecht Stadspolders 22:15No data—
Sun 25 OctDordrecht Stadspolders 22:15No data—
Sat 24 OctDordrecht Stadspolders 22:14No data—
Sat 17 OctDordrecht Stadspolders 22:15No data—
Sun 11 OctDordrecht Stadspolders 22:15Partial coverage0 min+1 min
Sat 10 OctDordrecht Stadspolders 22:14Partial coverage0 min—
Sun 4 OctDordrecht Stadspolders 22:14No data—
Sat 3 OctDordrecht Stadspolders 22:14No data—
Sun 27 SeptDordrecht Stadspolders 22:14No data—
Sat 26 SeptDordrecht Stadspolders 22:15No data—
Sun 20 SeptDordrecht Stadspolders 22:21No data—
Sat 19 SeptDordrecht Stadspolders 22:14No data—
Sun 13 SeptDordrecht Stadspolders 22:15No data—
Sat 12 SeptDordrecht Stadspolders 22:15No data—
Sun 6 SeptDordrecht Stadspolders 22:14No data—
Sat 5 SeptDordrecht Stadspolders 22:14No data—
Sun 30 AugDordrecht Stadspolders 22:15No data—
Sat 29 AugDordrecht Stadspolders 22:14No data—
Sun 23 AugDordrecht Stadspolders 22:14No data—
Sat 22 AugDordrecht Stadspolders 22:15No data—
Sun 16 AugDordrecht Stadspolders 22:14No data—
Sat 15 AugDordrecht Stadspolders 22:15No data—