The Mazda CX-6e in this catalogue has one generation and zero named versions, so a “which version to buy” answer can only be written from that fact: there is nothing in the data to rank.
The Mazda CX-6e is listed here as a 1 generation model, body SUV 5-doors, in production from 2025-04-01, with production stop not measured (still open in the data). Generation key 8684 carries modifikaciy: 0 and an empty versions list. That is the whole comparison set: one generation, zero versions. There is no 4.0 AT, no 3.3 AT, and no second name that would need a horsepower split.
The Mazda CX-6e in this catalogue has one generation and zero named versions, so a “which version to buy” answer can only be written from that fact: there is nothing in the data to rank.
# Mazda CX-6e: which version to buy (and why the catalogue cannot rank one)
The Mazda CX-6e is listed here as a 1 generation model, body SUV 5-doors, in production from 2025-04-01, with production stop not measured (still open in the data). Generation key 8684 carries modifikaciy: 0 and an empty versions list. That is the whole comparison set: one generation, zero versions. There is no 4.0 AT, no 3.3 AT, and no second name that would need a horsepower split. Any “buy this trim” ranking that invented a version name would break the modification-page anchors this catalogue uses.
This text is not a second general overview. It is the buyer question: which CX-6e version, and why. With empty version rows, the honest answer is that no version is selectable from these numbers, because no version is present. Arithmetic on power, torque, litres, weight, and drive is allowed in this series — but arithmetic needs at least two measured figures. Here the operands are missing.
CX-6e generations: what changed (and what did not)
1 generation (key 8684)
1 generation of the Mazda CX-6e starts 2025-04-01. The end date is not measured. The body is SUV 5-doors. Count of versions in this generation: 0. Restyling is not listed as a separate generation and is not listed inside this one either: there is no restyle row in the data.
Because the catalogue has only 1 generation, there is no generation-to-generation delta to compute. You cannot say the later car gained litres, lost kilograms, or changed drive: there is no later car in the file. The “what the extra money buys” question between generations is empty for the same reason: there is no second generation and no prices in the launch data.
A reader who expects “11th generation” repeated under restyles will not find that pattern here. 1 generation appears once. Treating a missing restyle as a second generation would be a cataloguing error, not extra information.
Mazda CX-6e specs: engine and gearbox table
People search CX-6e specs and CX-6e engine. The table below is the version grid as the data allows it. Every cell that is not in the launch object is not measured. There are no version names to print exactly, because the list is empty.
| Version (exact catalogue name) | hp | Nm | Displacement | Fuel | Cylinders | Layout | Boost | Gearbox | Drive |
|---|---|---|---|---|---|---|---|---|---|
| (no named version in data — versions: []) | not measured | not measured | not measured | not measured | not measured | not measured | not measured | not measured | not measured |
Do not read a blank table as “this SUV has no engine in the real world.” Read it as this catalogue row has no engine fields. Cylinder count and layout are taken only from version data; they are not filled from outside knowledge. Fuel and gearbox labels would have been taken as English tags from the data (Gasoline, Automatic, and similar). Those tags are not present, so they stay not measured.
With 0 versions, there is also no pair of identical names that would need a horsepower disambiguation (the Land Cruiser case of two 3.3 AT rows at different hp does not occur).
CX-6e performance: 0-100, top speed, mpg
0-100, top speed, and fuel use are not measured for every missing version. Combined, urban, and highway consumption are not measured. mpg as a converted figure is not computed, because there is no litres-per-distance input to convert.
A sentence such as “the stronger CX-6e is X seconds faster” would require two 0-100 values. Those values are not in the data, so that sentence is not written. “Not measured” is the value, not a skip. Skipping would look like the parameter does not exist for an SUV.
CX-6e dimensions, weight, ground clearance, tank, wheels
Kerb weight is not measured. Gross weight is not measured. Ground clearance is not measured. Fuel tank volume is not measured. Wheel sizes are not measured. Length, width, height, and wheelbase are not measured.
Weight per horsepower is the usual buyer ratio in this article series: kerb weight divided by hp. That ratio is not measured because both numerator and denominator are not measured. Power per litre (hp divided by displacement in litres) is not measured for the same reason. You cannot rank “the lighter CX-6e” against “the denser engine” until those two numbers exist on named versions.
Ground clearance comparisons between versions are also not measured. Tank size comparisons are not measured. Wheel-size splits are not measured.
CX-6e problems and reliability
Problems and reliability are not in the launch data. No failure rates, no campaign counts, no “years to watch.” This section does not invent workshop lore. What the data does support is a coverage statement: a model that entered the file on 2025-04-01 as 1 generation with 0 versions has no version-level reliability split. You cannot say the automatic is worse than the manual, or AWD is heavier on consumables, because gearbox and drive are not measured and unnamed.
If later catalogue drops add named versions, reliability still must not be back-filled from memory. Until those rows exist, treat problems and reliability as not measured.
Which CX-6e version to choose
What you can actually choose today in this file
Choice requires a list. The list is empty. Therefore no CX-6e version is recommended, not because all versions are equal, but because none are named. Recommending a phantom AT or AWD row would mint a link anchor that does not exist.
The only structured object you can “choose” is 1 generation itself: Mazda CX-6e, SUV 5-doors, on sale in this dataset from 2025-04-01, production end not measured. That is a generation lock, not a version lock.
Comparisons that are allowed — and why they collapse
This series is built on arithmetic:
- power per litre = hp / displacement
- weight per hp = kerb weight / hp
- extra output = hp(A) − hp(B)
- extra torque = Nm(A) − Nm(B)
All of those operations are allowed when both sides are in the data. For the CX-6e they cannot be evaluated. Division by a missing displacement is not a number. Subtracting two missing hp values is not a number. Reporting “0 versions” as if it were a performance figure would also be wrong: 0 is the count of modifications, not horsepower.
What “the extra money buys”
Prices are not in the data. The article does not quote list prices, packs, or “worth the upgrade.” Even if prices existed, upgrade value still needs two versions. With modifikaciy: 0, there is no paid step from a base engine to a stronger one.
Generation change: what 1 generation did not replace
There is no generation 2 in generations. Nothing “replaced” 1 generation. Body type did not move from another catalogue body into SUV 5-doors across a generation boundary, because there is only one boundary: the start date 2025-04-01. If a future generation is added, the buyer comparison should be: years, body English label, version count, then hp / litre and kg / hp on exact version names. That future table is not this table.
How to read a later update without breaking names
When versions appear, they must be cited exactly as stored (4.0 AT, 3.3 AT, and so on). If two rows share a name, split them by hp. Until that happens, do not alias the empty list as a single “standard CX-6e.” An unnamed standard is still not a version key.
Practical buyer takeaway (from these numbers only)
- Model: Mazda CX-6e
- Generations in file: 1
- Generation name: 1 generation
- Start: 2025-04-01
- Stop: not measured
- Body: SUV 5-doors
- Versions: 0
- Engines, hp, Nm, fuel, cylinders, layout, boost, gearbox, drive: not measured
- 0-100, top speed, consumption / mpg: not measured
- Weights, clearance, tank, wheels: not measured
- Price: not in data (not used)
Which version to buy: none can be ranked. Why: the catalogue has no version rows, so every comparison metric is not measured. Wait for named modifications; then rank them with hp per litre and weight per hp on those exact names. Until then, treating the CX-6e as a one-box “buy any” SUV would hide the empty grid instead of reporting it.