Address characteristics of persons who are or have been registered in the municipal population registers (01-01-2018 - 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 (01-01-2018 - 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
DGA, Adresbewoning, Microdata, Data Governance Act, Adres, Verhuizing, ODISSEI
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 file is part of CBS’s System of Social Statistical Files (SSB). The file is of the bus type. Bus type means that the data file (the component) has a form in which in a record (a row in the file) attributes are attached to an entity 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 shall 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/nl-nl/onze-diensten/maatwerk-en-microdata/microdata-zelf-onderzoek-doen ### Methodology When do you use this file? To retrieve information about people’s address at a certain reference date or in a certain level period and add it to the analysis file. Advice for use: The information about the last year in a version is consistent with the information published on StatLine by Team Demography. If information has to match the final information previously published on StatLine, use a coordinated version of the component (the component runs until 31 December JYJJ-1 00:00). Although the coordinated component contains information on 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 output. In all other cases, the most recent uncoordinated version can be used. Also, with the same component, a single analysis file with multiple periods can be created at the same time. Some examples: Level moment Status figures Component 1-1-2015 coordinated according to StatLine, 2014 31-5-2013 coordinated according to StatLine, 2013 2012 according to StatLine coordinated, 2011 If there is no need to connect to StatLine figures, the uncoordinated version can be used. This file is NOT suitable to determine the annual number of removals as published (once) by Team Demography. There are two reasons for this: — all changes relating to past messages, which became known in a later year, have been processed in the GBAADRESOBJECTBUS also in older years until the file has coordinated its status; — messages fulfilled within demographic statistics are not always counted in the year of event but in the year of receipt. Within the GBAADRESOBJECTBUS it is not possible to distinguish this. For determining the annual number of persons moved, such as those published (once) by the Demography team, reference is made to the GBAADRESGEBEURTENISBUS component. This file is not optimal to deduce the state of the population on 1 January of a given year, as published (once) by team Demography. For this purpose reference is made to the component GBASTANDBEVOLKINGYYJTABVV. ### Population Addresses of persons who have been registered in the municipal population registers since 1 October 1994. Also contains addresses of persons who were registered in the municipal population registers before 1 October 1994. This population once-residents is not complete. These include emigrants who have already emigrated before the start of the BRP (at the time still 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