Address characteristics of persons who are or have been registered in the municipal population registers (from 01-01-2023)

Open data API in a single place

Provided by Centraal_Bureau_voor_de_Statistiek

Get early access to Address characteristics of persons who are or have been registered in the municipal population registers (from 01-01-2023) API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
Adres, Data Governance Act, Verhuizing, ODISSEI, Adresbewoning, DGA, Microdata
Quality scoring

Dataset description

Addresses of persons located in the Netherlands with date beginning and date end of each period of address residence. The component is a coordinated version and contains information until 31 December YYYY. Only the information for the last year has been coordinated. The information in the component will in principle no longer change. The database is part of Statistics Netherlands' System of Social Statistical Files (SSB). The file is of the bus type. Bus type means that the data file (component) has a form in which attributes are associated with an entity in a record (a row in the file) using a time key. The time key consists of a start date and an end date. When a change occurs in one or more attributes, a new record is created. There should be no overlap in the time keys of successive records for a specific entity. More information on how to access the data: > https://www.cbs.nl/en-en/our-services/custom-and-microdata/microdata-self-research ### Methodology When do you use this file? To retrieve information about the address of persons on a certain reference date or in a certain reference period and add it to the analysis file. Advice for use: The information for the last year in a version is in line with the information published on StatLine by team Demography. If information has to be linked to final information already published on StatLine, you use a coordinated version of the component (the component runs until 31 December YYYY-1 00:00). Although the coordinated component contains information over a series of years, only the last year in the version of the component is final. This means that a different version (year) of the coordinated component should be used for each year of output. In all other cases, the most recent non-coordinated version may be used. The same component can also be used to create a single analysis file with multiple periods at the same time. Some examples: Monitoring moment Status figures Component 1-1-2015 coordinated according to StatLine, 2014 31-5-2013 coordinated according to StatLine, 2013 2012 coordinated according to StatLine, 2011 If it is not necessary to connect to StatLine figures, the non-coordinated version can be used. This file is NOT suitable for determining the annual number of moves as published (once) by the Demographics team. There are two reasons for this: - all changes relating to messages from the past, which became known in a later year, have been incorporated in the GBAADRESOBJECTBUS also in older years until the status has been coordinated by the file; - within the demographic statistics, fulfilled messages are not always counted in the year of event but in the year of receipt. Within the GBAADRESOBJECTBUS it is not possible to distinguish between them. To determine the annual number of people moved, as (once) published by the Demographics team, reference is made to the GBAADRESGEBEURTENISBUS component. This file is not optimal to derive the state of the population on 1 January of a given year, as (once) published by the Demographics team. For this, reference is made to the component GBASTANDPOPULATIONYYYTABVV. ### Population Addresses in the Netherlands of persons who have been registered in the municipal population registers since 1 October 1994. It also contains addresses of persons who were registered in the municipal population registers before 1 October 1994. This population of once-residents is not complete. For example, emigrants who had already emigrated before the start of the Personal Records Database (BRP) (at the time still Municipal Personal Records Database (GBA) ).
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks