Ferrari SF90 XX: which version to buy and why

If you are trying to choose a Ferrari SF90 XX by comparing named versions, this catalogue currently gives you one generation, one body, and zero named versions. The model key is 3741, the English name is SF90 XX, the brand is Ferrari, production of 1 generation starts on 2023-06-01, the end date is not measured, the body is Coupe, and the version count is 0.

If you are trying to choose a Ferrari SF90 XX by comparing named versions, this catalogue currently gives you one generation, one body, and zero named versions. The model key is `3741`, the English name is SF90 XX, the brand is Ferrari, production of 1 generation starts on 2023-06-01, the end date is not measured, the body is Coupe, and the version count is 0. There is therefore no second row of horsepower, newton-metres, litres, fuel, cylinders, layout, boost, gearbox, or drive to subtract from a first row. Arithmetic on the given counts is: 0 versions ÷ 1 generation = 0 versions per generation. That is the whole choice set in this file.

This is not a general model tour. It is a buyer’s comparison against an empty version list. Every numeric claim below is either a count from that list or an explicit not measured.

Generations: what changed between generations (there is only one)

1 generation (English label from the data: 1 generation) is the only generation on the card.

Buyer implication: you cannot prefer “the current generation over the previous one,” because previous generations in this dataset equal 1 − 1 = 0. You also cannot prefer a restyle over a pre-restyle car using these rows, because restyle rows are not present. The only generation-level choice this file supports is: the Coupe of 1 generation from 2023-06-01, with no named sub-variants attached.

If a later catalogue drop adds a second generation, the comparison would be start year versus start year and version count versus version count. That second generation is not in the data, so that comparison is not measured.

Specs: engines and named versions (the comparison table)

People searching for SF90 XX specs, engine, horsepower, and gearbox are looking for named versions exactly as they appear in the database (for example the pattern «4.0 AT»). This model’s `versions` array is empty. There are 0 names to print as link anchors.

Version name (exact)hpNmDisplacementFuelCylindersLayoutBoostGearboxDrive
(no named version in data)not measurednot measurednot measurednot measurednot measurednot measurednot measurednot measurednot measured

There is no «4.0 AT», no second «4.0 AT» to split by horsepower, and no pair of names that differ only in output. Power-per-litre is not measured / not measured. Weight per horsepower is not measured / not measured. Extra displacement between versions is not measured − not measured. Extra horsepower between versions is not measured − not measured.

Do not fill those cells from memory of other Ferrari models. Cylinder count and layout, when they exist, come from version rows. Here those rows do not exist, so the engine configuration is not measured, not inferred.

Buyer implication: you cannot choose “the stronger engine” or “the smaller engine” from this page. The extra money for a higher-output row is not measured because there is no second output figure.

Performance and economy (0–100, top speed, mpg)

For every missing version, acceleration, top speed, and fuel use are not measured.

A comparison of “which version is quicker” needs at least two 0–100 figures. Number of 0–100 figures in the data: 0. Difference between fastest and slowest: not measured. A comparison of “which version uses less fuel” needs at least two consumption figures. Number of consumption figures: 0. Difference: not measured.

If a seller quotes a time or an mpg number, that number is not in this catalogue file. This article does not import it.

Buyer implication: you cannot rank versions by sprint, by top speed, or by mpg using these facts. Those rankings are not measured.

Dimensions and weight (kerb, gross, clearance, tank, wheels)

The generation object lists body Coupe and does not list kerb weight, gross weight, ground clearance, tank size, or wheel sizes.

Weight per horsepower cannot be ranked across versions: both weight and horsepower are not measured, and version count is 0. Clearance cannot be used to pick a “higher” versus “lower” car: only one body is listed, and clearance is not measured. Tank size cannot be used to pick range: tank is not measured, consumption is not measured.

Buyer implication: body type does not split the range. There is 1 body type (Coupe), so Coupe minus other bodies = no other bodies in the file. You are not choosing between Coupe and another labelled body on this card.

Problems and reliability

This dataset has no problem counts, no reliability scores, no recall counts, and no service-interval numbers. Those values are not measured. You cannot pick a version because it “fails less”: failure rates by version are not measured, and there are 0 versions to group failures by.

Buyer implication: reliability is not a differentiator in this file. Do not treat silence as “no problems exist.” Silence here means the field was not supplied.

Which version to choose

Work only with the arithmetic the file allows.

1. How many versions can you shortlist? 0. A shortlist of named catalogue versions does not exist yet. You cannot say “buy the 299 hp one rather than the 309 hp one,” because those two outputs are not on this card, and no duplicate names need splitting by power.

2. How many generations can you shortlist? 1. There is no older generation with a lower version count or a different body to trade against. Generation keys in the data: 1 (`kluch` 8068). Extra generations you could wait for: not measured.

3. What did a later generation change? Nothing in this file, because a later generation is not listed. Changed horsepower: not measured. Changed body count: the listed body count is 1 (Coupe). Changed version count: 0 versions in 1 generation.

4. What does extra money buy? Prices are not in the data and are not used. Even without price, “extra money” in spec terms means extra hp, extra Nm, extra equipment rows. Extra hp = not measured. Extra Nm = not measured. Extra named gearbox or drive = not measured. The extra you can count is 0 additional versions and 0 additional bodies.

5. Power per litre and weight per horsepower. Both need version-level numbers. Version-level numbers present: 0. Those ratios are not measured. They cannot pick a winner.

6. Fuel and drive layout as a filter. Fuel label, drive label, and gearbox label are taken only from version rows (Gasoline, Automatic, AWD, and similar English labels as stored). With 0 rows, fuel is not measured, drive is not measured, gearbox is not measured. You cannot filter “only Automatic” or “only a given drive” against this card.

7. Practical choice this file does support. If you need a Ferrari SF90 XX as defined here, the only generation-and-body pair in the catalogue is 1 generation, Coupe, in production from 2023-06-01, end date not measured, with 0 named modifications. That is not a version recommendation; it is the statement that version-level recommendation is empty.

8. What would change the recommendation. If a later data drop adds two named versions, the buyer test becomes: same name distinguished by hp if names collide; otherwise compare hp, Nm, displacement, and the labelled fuel / cylinders / layout / boost / gearbox / drive fields exactly as stored; then compute hp per litre and, if kerb weight is present, kg per hp. None of those fields are present now.

Until those rows exist, choosing “which SF90 XX version to buy” from this catalogue is choosing among 0 named versions. The honest answer is: no named version is measured here, so a version-to-version buy recommendation is not measured. The only facts you can hold onto while you wait for version rows are: Ferrari, SF90 XX, 1 generation, start 2023-06-01, stop not measured, body Coupe, modifications 0.