Dutch Test Data Generator
Create synthetic Netherlands profiles for forms, demonstrations and localization tests.
Preparing your test data…
Your first record will appear here shortly.
Copy individual values or export the entire result.
Synthetic identities; domains, addresses and numbers may coincide with real values. Do not contact or send payments.
Testing Netherlands interfaces
This locale uses nl definitions for names and presentation formats. Test text lengths, input handling, exports and Unicode support. City, region and available postal codes come from the same GeoNames locality. See the generated quality note for postal coverage; street and house number remain synthetic.
Testing Netherlands forms
Dutch fixtures expose a common form-design mistake: treating every postcode as a number. Use a profile for linked locality data, then a small editorial fixture to test letter handling, spaces and the way your application stores address components.
Generator locale: nl. Suggested application display locale: nl-NL. These are separate settings; this guide does not change the generator’s output.
Alphanumeric Dutch postcodes
The UPU describes four digits followed by two letters, with a space between the numeric and alphabetic parts. Keep letters and spacing in a text field. Matching this pattern does not establish that the postcode belongs to the chosen locality, street or house number.
House numbers and multi-part names
Keep street and house-number information in fields that can preserve suffixes. Include a deliberately multi-part family-name fixture such as van Dalen to check that splitting, sorting or capitalization does not discard part of the input. That fixture is illustrative, not a model for every person in the Netherlands.
Locale display and payment-form checks
Use Dutch display formatting separately from the stored date or contact value. Save the country with phone samples and isolate outbound messages. For IBAN-related forms, use the banking tools and retain their check-level notes; an address profile is not proof of a bank relationship.
A deliberate regression fixture
Editorial regression fixture — no delivery claim country: NL family_name_input: "van Dalen" postal_code_input: "1234 AB" (format-only example) house_number_input: "12A" expected: retain letters and suffixes through save and CSV import
These editorial inputs are for controlled tests. They are not verified addresses, guaranteed unassigned contact details, or automatically generated examples.
- 01
Postal field
Accept text input and retain the alphabetic part.
- 02
House number
Keep a suffix through editing instead of coercing the field to an integer.
- 03
Name parts
Preserve the entered family-name string when presenting or sorting it.
Address reference: UPU addressing guide: Netherlands. Reviewed 4 October 2026. Postal presentation rules are not universal rules for storing personal names.