Data Freshness Issue – RDW Open Data Datasets (vkij-7mwc vs m9d7-ebf2)
Abhishek Joshi
Dear RDW Open Data Team,
We are currently using and synchronizing the following two datasets:
- vkij-7mwc – Open Data RDW: Keuringen
- m9d7-ebf2 – Open Data RDW: Gekentekende_voertuigen
Our objective is to provide end users with an accurate list of vehicles requiring maintenance.
Initially, we relied on the APK expiry date from the m9d7-ebf2 dataset. However, as this dataset did not appear to refresh frequently enough for our use case, we transitioned to using the vkij-7mwc dataset to derive the maintenance (inspection) date.
At present (08-04-2026), we are experiencing a discrepancy in data freshness. Although the vkij-7mwc dataset indicates a last refresh date of 07-04-2026, it does not seem to reflect the most recent values.
Example scenario:
- Kenteken: ZV657G
From vkij-7mwc (Keuringen):
- Vervaldatum keuring: 2025-06-14
From m9d7-ebf2 (Gekentekende_voertuigen):
- Vervaldatum APK: 2026-06-14
In this case, the m9d7-ebf2 dataset appears to contain the correct and updated value, while vkij-7mwc does not reflect the latest information.
Given that this data is critical for informing end users about vehicle maintenance requirements, we kindly request your guidance on:
- The expected refresh frequency of the vkij-7mwc dataset
- Whether there are known delays or limitations in updating this dataset
- Which dataset should be considered the most reliable source for APK/inspection expiry dates
We would greatly appreciate your support in clarifying this, as it directly impacts the accuracy of information shared with our users.
Thank you for your assistance.
Kind regards,
Abhishek Joshi