Suzuki
Samurai Hardtop
Hatchback.
- n/a
- Registered
- 2 countries
- On the road in
- Top 90%
- Worldwide popularity
- #2362
- in New Zealand
Popular in
Rank in each official register
Canonical id car/suzuki/samurai-hardtop ·
dataset 2026.11.9, CC-BY 4.0,
from real registration and fleet counts.
On the record
Where the Suzuki Samurai Hardtop 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/car/suzuki/samurai-hardtop/full
Generations, engines and specs
Coming. Not in the record yet.
Today the Suzuki Samurai Hardtop 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 Suzuki Samurai Hardtop 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 Suzuki, then the Samurai Hardtop or any of Suzuki's 76 other cars, from every make on record. Your country's popular cars 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 Suzuki Samurai Hardtop as JSON, one request away: its canonical id, where it is registered and how popular it is.
GET /api/v1/vehicles/car/suzuki/samurai-hardtop/full
2 credits per call. Unknown ids are free. Free accounts start with 100 credits.
GET …/car/suzuki/samurai-hardtop/full free plan response
{
"id": "car/suzuki/samurai-hardtop",
"name": "Samurai Hardtop",
"make": {
"id": "suzuki",
"name": "Suzuki"
},
"kind": "car",
"body_type": "hatchback",
"availability": [
"nz",
"us"
],
"regions": [
"na",
"oc"
],
"popularity": {
"global_decile": 7,
"mass_decile": 9,
"rarity": "average"
},
"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
Suzuki Samurai Hardtop as this row. Free with an account: download it, store it, show it, with a credit line.
- kind
- car
- make_slug
- suzuki
- make_name
- Suzuki
- model_slug
- samurai-hardtop
- model_name
- Samurai Hardtop
- body_types
- hatchback
- countries
- nz|us
- regions
- na|oc
- global_popularity_decile
- 7
- mass_popularity_decile
- 9
- 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 Suzuki Samurai Hardtop owner in New Zealand types a plate like this into your form. Check it is a valid format in New Zealand, get it back as issued, and draw it on its real design.
More cars from Suzuki
All Suzuki models →Swift
Hatchback · 1983–now
Vitara
SUV · 1989–now
SX4
Hatchback · 2006–2026
Jimny
SUV · 1998–now
Grand Vitara
SUV · 1998–2026
Ignis
SUV · 2000–2025
S-Cross
SUV · 2022–now
Alto
Hatchback · 1981–2024
Popular in New Zealand
All cars in New Zealand →Other popular hatchbacks
All hatchbacks →Something off about this record? Fix it on GitHub. The catalog is open data, and corrections make it better for everyone.