Guides: Data source and freshness
Data source and freshness
What the Motorbay API serves, where it comes from, and how to tell how old it is.
The source
The data comes from Motorstyrelsen's weekly public statistics extract of the Danish Motor Register (Det Digitale Motorregister, DMR). Motorstyrelsen is the Danish Motor Vehicle Agency. Motorbay is not affiliated with Motorstyrelsen, and the data is provided as-is.
We import the extract as it is registered. We convert types and normalize identifiers. We don't correct, guess or fill in values.
The extract holds no owners, keepers or other people, and neither does the API.
It's weekly, not real time
Motorstyrelsen publishes a new extract about once a week. We import it after it's published. A change registered at Motorstyrelsen reaches the API after their next extract and our import, usually within a week. The API is not real time.
The previous extract stays live while an import runs, so the API doesn't pause during imports.
Check how old the data is
GET /v1/dataset describes the extract being served:
curl -H "X-Api-Key: $MOTORBAY_API_KEY" \
"https://api.motorbay.app/v1/dataset"{
"sourcePublishedAt": "2026-09-21T04:43:39+00:00",
"importedAt": "2026-09-21T17:01:50.9719+00:00",
"vehicleCount": 4869,
"source": "Motorstyrelsen, weekly public statistics extract (ESStatistikListeModtag)"
}| Field | Meaning |
|---|---|
sourcePublishedAt |
When Motorstyrelsen published the extract |
importedAt |
When our import of it finished and it went live |
vehicleCount |
How many vehicles the extract holds. null for older imports |
source |
Where the data comes from |
Before the first import has finished, it answers 503 with the code DatasetNotLoaded.
Every response to a request with a valid key also carries a Motorbay-Data-As-Of header with the extract's publication time, so you can record it next to what you store:
Motorbay-Data-As-Of: 2026-09-21T04:43:39ZWhen importedAt changes, a new extract is live. That's a good moment to refresh anything you cached.
Reading the data
- IDs are strings. They hold Motorstyrelsen's numeric identifiers, for example
"9000000006320919". Treat them as opaque text. Don't parse them as numbers: they don't all fit in a JavaScript number. - Calendar dates are
YYYY-MM-DDwith no time zone, in fields whose names end inOn, such asfirstRegisteredOn. - Points in time are ISO 8601 with a UTC offset, in fields whose names end in
At, such asstatusUpdatedAt. The offset isn't alwaysZ:/v1/datasetsends+00:00, and some vehicle fields send+02:00. Parse the offset rather than assuming UTC. - Missing values are
null, never left out. Some fields come with a flag such asisMaximumPowerUnavailable, which istruewhen the register marks the value as not reported. - Lists are never
null. An empty list is[]. - Numbers keep Motorstyrelsen's units, such as kg, mm and kW. Each field's unit is in the API reference.
- Status values are camelCase, such as
registeredandderegistered. Motorstyrelsen adds values over time, so handle values you don't know. - Reference data has two names. Kinds, colors, usages and other reference data carry
nameandoriginalName.originalNameis always Motorstyrelsen's Danish text, for examplePersonbil.nameis the same Danish text, or English when you sendAccept-Language: en, for examplePassenger car. Makes, models, variants and designation types are proper names and are never translated. - Values are as recorded. We pass on what Motorstyrelsen records and don't correct it, so a value can be wrong.
modelYearis one: a few vehicles have a model year that can't be right, such as 2112 for a car first registered in 2012.modelYearPlausibleon/calculatedflags them. Search and statistics filter onmodelYearas recorded. - Ignore fields you don't know. We add fields without a new API version.
Every vehicle stays in the data
Deregistered, scrapped and exported vehicles stay in the data with their status. Check registrationStatus and status if you only want vehicles on the road.
Values Motorbay calculates
GET /v1/vehicles/{vehicleId}/calculated returns values that are not in Motorstyrelsen's extract. Motorbay calculates them from the raw values, which stay unchanged on the other vehicle resources. Each value is null when the data it needs is missing. A recorded value that no vehicle of its kind can have counts as missing: a power outside 1 to 1,000 kW for a car or van (1 to 400 for a motorcycle, 0.1 to 8 for a moped, 0.1 to 2,000 for other kinds), such as an engine recorded in W, or a km/l outside 1 to 60 for a petrol or diesel car or van that isn't a plug-in hybrid. The same goes for a car's or van's Wh/km outside 50 to 1,000 or CO2 over 1,000 g/km, and a motorcycle's displacement over 3,000 cm³. A km/l or Wh/km of 0 or below is a field not filled in, so the own weight estimate applies. CO2 has no estimate: a negative CO2 is unknown, and so is 0 on a petrol or diesel car, while an electric car's 0 counts as 0 g. The vehicle resources still serve each value as Motorstyrelsen records it.
horsepoweris metric horsepower (hk):maximumPowerin kW times 1.35962, rounded to a whole number.ageis{ "years", "months" }fromfirstRegisteredOnto today's Danish date (calculatedOn). For a deregistered vehicle it is counted to the day it was deregistered.ageUntilsays which:todayorderegistered.annualKilometersis the odometer at the latest inspection (in km) divided by the years from first registration to that inspection. It isnullwhen the inspection was less than a year after first registration.powerToWeightis kW per kg ofownWeight, to 3 decimals.isElectricistruewhen El is the only fuel type.isPluginHybridistruewhen a combustion fuel is recorded with an electric consumption. The extract records most plug-in hybrids as one Benzin or Diesel row with an electric consumption. The extract can't tell a mild or full hybrid from a petrol or diesel car, so there is noisHybrid.modelYearPlausibleisfalsewhenmodelYearis after the extract's year plus one, or before 1885, the year the first motor car was built. It istrueotherwise, also when the model year is older thanfirstRegisteredOn, which an imported or late registered vehicle can be.modelYearitself is never changed.modelYearFromVinis the manufacturer's model year from the VIN, next to the register'smodelYear, which is never changed.yearis read from the year code at position 10 only when the check digit at position 9 is right and the year lies within a year offirstRegisteredOn, and isnullotherwise, with areason. EU law doesn't require a year at position 10, so many European vehicles get none, and so can a late import.statusismatches,differs,registerImplausible(whenmodelYearPlausibleisfalse),fillsMissingorunknown. A manufacturer's model year can start in the calendar year before, sodiffersdoesn't mean either is wrong. Search, filters and statistics keep using the register'smodelYear.manufacturerRegionandmanufacturerCountrycome from the first two characters of the VIN and the country table in ISO 3780, for exampleeuropeandSE. The country is where the manufacturer code was assigned, usually where the vehicle was made. We don't name the manufacturer from the VIN.periodicTaxesis the periodic tax on a passenger car, van or motorcycle for a tax period starting today, at that year's rates: green ownership tax by km/l or g CO2/km, or weight tax, with the equalisation tax and the particle supplement.lineshas each amount with itsperiodMonthsand the act it comes from. The km/l is the one recorded on the primary fuel row, and a WLTP value is multiplied by 1.21 as the act says.notIncludednames what the extract can't show, such as exemptions. Buses, trucks and trailers arenotCovered, andstatusisunknown, with areason, when the extract lacks what the rule needs. It is not Motorstyrelsen's bill.energyClassis the energy class,A+++toG, of a petrol or diesel passenger car or van, read from its recorded km/l with the energy labelling order in force on the day it was first registered. From 1 Jan 2019 that is the WLTP table, before it the NEDC table, and the classes aboveAstart on 1 Aug 2012. A class is only given when the register records the test procedure of the value, since a value without one can be estimated from the weight, so many older vehicles have none. Plug-in hybrids, electric and gas vehicles have no class.estimatedNextInspectionis an estimate of the last day to present the vehicle for its next periodic inspection (dueBy), from its kind, use, permits, first registration and latest inspection, with the rules in force on that day.statusisupcomingoroverdueon today's Danish date,notRequiredfor vehicles that aren't periodically inspected or are deregistered, orunknownwhen the extract lacks what decides it.overdueis as of the latest extract, since an inspection done after it isn't in it yet. The extract holds only the latest inspection, so a vehicle with none on record isoverduefor 15 weeks after its first deadline, when the plates are taken, andunknownafter. Færdselsstyrelsen's summons sets the real deadline.
Vehicle history
GET /v1/vehicles/{vehicleId}/history, or include=history on a lookup, returns what changed about a vehicle from one weekly extract to the next: its registration numbers (plates), statuses, registrationStatuses and inspections, each newest first.
- History goes back to the extract of 20 Sep 2026. Each extract holds only a vehicle's state that week, so history is the vehicle's state in the first extract we hold for it, then what we have seen change since.
observedSinceis that extract's day: 20 Sep 2026 for a vehicle in the register then, later for one that came into it after. The oldest item in each list is what the vehicle had in that extract, not necessarily a change in the week before it. A plate or inspection from before it isn't missing from the register: we have no extract from then. A vehicle with no history yet has empty lists andobservedSince: null. observedOnis the day of the extract a value was first seen in.changedOnis the day the register gives for the change, when it gives one. Plates have none, so a plate changed in the week before itsobservedOn, or, for the oldest plate, at any time before.- A plate in
platesmay be on another vehicle now. Registration numbers are reused, and personal plates move between vehicles.plate: nullmeans the plates were taken off. inspectionshas each new inspection with itsodometerReadingin thousands of km. The latest is also at/inspection. Withunits=imperialeach one hasconverted, as on/inspection.blocksandleasingPeriodshave each set of blocks or leasing periods the vehicle had, newest first: the whole set each time it changed, and an empty set when none was left. A block is named as on/blocking-reasons, and a period hasvalidFromOnandvalidUntilOnas on/leasing-periods. These two lists started later than the others, so they have their own start dates,blocksObservedSinceandleasingPeriodsObservedSince, the same for every vehicle. The first set in each list is what the vehicle had on that day, not a change. Until then both dates arenulland the lists are empty, which says nothing about the vehicle.- A week we take back is never shown. If an extract turns out to be wrong and we go back to the week before, its changes leave the history too.
One call is one request, on every plan.
Look up a vehicle by registration number
GET /v1/vehicles/plate/{plate} looks up a vehicle by registration number. Registration numbers are reused, and personal plates move between vehicles, so several vehicles in the register can have had the same one.
- Input is trimmed, uppercased, and spaces and hyphens are removed, so
ab 12 345andAB-12345findAB12345. - Only A to Z, 0 to 9, Æ, Ø and Å are accepted, at most 10 of them. Anything else is a
400withRegistrationNumberInvalidundererrors. - If several vehicles have had the registration number, you get the one currently registered with it. If none is, you get the most recent one, and its
registrationStatustells you it's no longer registered. The answer is the same on every request. GET /v1/vehicles?registrationNumber=AB12345lists every vehicle that has had it, in the same order, so the first item is the one the lookup returns.
Didn't find the answer? Email support@motorbay.app.