GMC Envoy
Years on record
The first and last year each official register has the GMC Envoy on record.
- Netherlands
- 2004
- Surviving fleet by first-registration year.
- Finland
- 2011–2013
- Surviving fleet by first-registration year.
Worldwide popularity
Measured from real registration and fleet counts, not clicks or hype.
Where it's been spotted
Evidence of real vehicles in each country's official register. Grey imports count, because they're real vehicles on real roads.
Powertrains on record
3 registers 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/gmc/envoy/full
Registration history
View as table
| 2004 | 2 |
| 2011 | 1 |
| 2013 | 1 |
From official registers, as of 2026.10.3. Bases differ per country, so never compare across panels.
Try the API
The GMC Envoy as JSON, one request away: its canonical id, where it is registered and how popular it is.
GET /api/v1/vehicles/car/gmc/envoy/full
2 credits per call. Unknown ids are free. Free accounts start with 100 credits.
GET …/car/gmc/envoy/full free plan response
{
"id": "car/gmc/envoy",
"name": "Envoy",
"make": {
"id": "gmc",
"name": "GMC"
},
"kind": "car",
"body_type": "hatchback",
"availability": [
"ca",
"fi",
"nl",
"us"
],
"regions": [
"eu",
"na"
],
"popularity": {
"global_decile": 8,
"mass_decile": 9,
"rarity": "rare"
},
"aliases": [],
"former_ids": [],
"years": null,
"era": null,
"enrichment": null,
"enrichment_gated": true,
"dataset_version": "2026.10.3",
"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.10.3"
}
}
On Developer
and up, enrichment carries production runs, variants, related models, powertrain counts, reference links and make facts.
More cars from GMC
Something off about this record? Fix it on GitHub. The catalog is open data, and corrections make it better for everyone.