Data Sources & Methodology

Last updated 2026-05-07. We re-publish this page whenever a source, refresh cadence, or check method changes.

Sources we read (authoritative only)

Source	What we use it for	Refresh cadence
Gemeente Amsterdam — Milieuzone	Active LEZ & ZE polygons, vehicle-class bans, transition rules, exemption categories, published fines (€130 / €320).	Weekly
RDW — Voertuiggegevens	Per-kenteken Euro class, fuel type, registration date, mass class, vehicle-category code (M1 / N1 / N2 / N3).	On request (per check)
Centraal Loket Milieuzones (CLM)	National permit / exemption look-ups for trades, refrigerated, medical, RDW-registered specials.	Daily
Per-municipal verordeningen (Rotterdam, Utrecht, Den Haag, Eindhoven)	Local ZE polygons, transition deadlines, exemption rules where they diverge from the national framework.	Weekly
OpenStreetMap (NL extract)	Street geometry for stop-to-zone polygon checks. We do not pull live traffic; routing is permitted-set / forbidden-set logic, not optimisation.	Monthly

What we do not read: Google Maps, paid carrier APIs, scraped traffic providers, or unauthenticated third-party LEZ databases. Fleetkeur outputs are derivable from public Dutch government data.

How a check works

Customer POSTs (or uploads) tomorrow’s stops + per-vehicle kenteken roster.
For each vehicle: RDW look-up → Euro class, fuel, registration date, vehicle category.
For each stop: which Dutch ZE/LEZ polygons (if any) the address falls inside, time-of-day restrictions if applicable.
Apply municipal ruleset to (vehicle, stop) pair: allowed · blocked · blocked-with-exemption-available.
Return JSON or PDF report; flag the stops that need re-assignment, suggest exemption-portal URLs where applicable.

Update cadence

Compliance datasets refresh weekly (Tuesday 04:00 CET) and on-event when a municipality publishes a verordening. Each rule entry carries a last_verified_utc timestamp and a link to the originating ordinance. The pilot report shows the timestamps so you can audit our reading.

What we do not promise

We do not promise legal indemnity. Fines remain the operator’s responsibility — see Terms §2.
We do not predict ordinances that haven’t been published yet. Where a transition is announced for a future date (e.g. ZE expansion 2027), we surface it; we do not fabricate near-term enforcement.
We do not currently route foreign-registered (non-NL) plates beyond category-level look-ups. Foreign-plate support is on the 2026-Q4 roadmap.

Bug bounty

If a Fleetkeur check returns a false-positive or false-negative on a documented Dutch ordinance, please email support@fleetkeur.com with the kenteken, stop, expected outcome, and ordinance citation. Confirmed compliance bugs earn a 1-month service credit per pilot or paying customer who reports first.