DFSK K01He
Van.
- n/a
- Registered
- 1 country
- On the road in
- Top 70%
- Worldwide popularity
- #61
- in Spain
Popular in
Rank in each official register
Canonical id van/dfsk/k01he ·
dataset 2026.11.9, CC-BY 4.0,
from real registration and fleet counts.
On the record
Where the DFSK K01He is on the road, and since when, from each country's official register.
Where it's been spotted
Evidence of real vehicles in each country's official register, with the model's rank there where the register counts it. Grey imports count, because they're real vehicles on real roads.
Powertrains on record
1 register with powertrain counts
Powertrain counts straight from official registers, each with what that register counts.
Building on it? The same record is one API call: /api/v1/vehicles/van/dfsk/k01he/full
Generations, engines and specs
Coming. Not in the record yet.
Today the DFSK K01He record holds its make, model, kind, body type, registration years, popularity and countries. We are building generations, engines and trims, and specs next, sourced and cited like everything else. Parts fitment and listing sites asked first.
Use the DFSK K01He in your product
In a booking or quote form, inside your app, in a listing or a page per vehicle. Same record, same id, everywhere.
A make and model dropdown for your form
Your customers pick DFSK, then the K01He or any of DFSK's 8 other vans, from every make on record. Your country's popular vans first, your language, an optional year step. One block to paste, no code to write, and it stays current with every release.
Try the API
The DFSK K01He as JSON, one request away: its canonical id, where it is registered and how popular it is.
GET /api/v1/vehicles/van/dfsk/k01he/full
2 credits per call. Unknown ids are free. Free accounts start with 100 credits.
GET …/van/dfsk/k01he/full free plan response
{
"id": "van/dfsk/k01he",
"name": "K01He",
"make": {
"id": "dfsk",
"name": "DFSK"
},
"kind": "van",
"body_type": null,
"availability": [
"es"
],
"regions": [
"eu"
],
"popularity": {
"global_decile": 3,
"mass_decile": 7,
"rarity": "common"
},
"aliases": [],
"former_ids": [],
"years": null,
"registration_years": null,
"era": null,
"enrichment": null,
"enrichment_gated": true,
"dataset_version": "2026.11.9",
"upgrade_url": "https://vehiclesdb.com/pricing",
"attribution": {
"source": "VehiclesDB",
"url": "https://vehiclesdb.com",
"license": "Identity layer: CC-BY-4.0; enrichment/resolution: proprietary. Display requires visible credit — see https://vehiclesdb.com/legal/attribution",
"dataset_version": "2026.11.9"
}
}
On Business
and up, enrichment carries production runs, variants, related models, powertrain counts, reference links and make facts.
One row of vehicles.csv
The open dataset (release 2026.11.9, CC-BY 4.0) holds the
DFSK K01He as this row. Free with an account: download it, store it, show it, with a credit line.
- kind
- van
- make_slug
- dfsk
- make_name
- DFSK
- model_slug
- k01he
- model_name
- K01He
- body_types
- ∅
- countries
- es
- regions
- eu
- global_popularity_decile
- 3
- mass_popularity_decile
- 7
- aliases
- ∅
- former_ids
- ∅
Credit required: <a href="https://vehiclesdb.com">Vehicle data by VehiclesDB</a>
Running a listing site or a page per vehicle? Sync new models into it with the API instead of re-importing files.
The plate next to it
A DFSK K01He owner in Spain types a plate like this into your form. Check it is a valid format in Spain, get it back as issued, and draw it on its real design.
More vans from DFSK
All DFSK models →Popular in Spain
All vans in Spain →Something off about this record? Fix it on GitHub. The catalog is open data, and corrections make it better for everyone.