How to compare vehicle specifications without mixing variants

Question and exact variants

When several captured records share a Toyota 4Runner fourth-generation name, how do you make sure every number in a comparison comes from the same variant? The captured source contains six modification records under generation 5359, with stable IDs 49798 through 49803. Only two names appear across them: “4.0 AT” (49798, 49799) and “4.7 AT” (49800, 49801, 49802, 49803). Four different records share the name “4.7 AT”, so a name cannot identify a record.

Select by stable record ID first, then check the fields that tell variants apart. For these records, the drivetrain field separates variants fastest. The source's English dictionary labels are RWD (code tdr-rear) and AWD (code tdr-4x4). This guide uses those labels exactly as recorded and does not rename AWD to anything else. Records 49798, 49801 and 49803 are labelled RWD. Records 49799, 49800 and 49802 are labelled AWD. Even name plus drivetrain label is not unique: two RWD records and two AWD records are both named “4.7 AT”. The record ID is the only reliable key.

Recorded specifications

Every captured row records the same engine type (Gasoline), transmission (Automatic) and fuel tank capacity (87 l), so those fields cannot tell variants apart. The fields that do differ between records include curb weight and full mass in kg, minimum clearance in mm, mixed fuel consumption with a recorded unit of l, maximum_power_hp, and engine_capacity. All six source cards also record identical production start and stop dates, so the production period does not separate them either.

Two fields need care. No unit is recorded for maximum_power_hp or engine_capacity. The field identifier and the marketing names 4.0 and 4.7 may suggest units, but they are not recorded measurements. Values such as 245 or 4664 are therefore shown here as bare numbers, with the note that no unit was provided.

Worked comparison or conversion

The clearest mixing trap in this set is a pair of records that share both a name and a drivetrain label. Records 49801 and 49803 are both named “4.7 AT” and both labelled RWD. Record 49801 has a maximum_power_hp of 235 (no unit recorded), a clearance_min of 231 mm and a mixed consumption value of 12.4 (unit recorded as l). Record 49803 has 273, 240 mm and no mixed consumption value. A search by name and drivetrain alone can return either card, so a comparison row can easily end up with 273 from one card and 12.4 from the other. That row describes a combination that no single record in the source contains.

The fix is procedural: assign one record ID to each comparison column, take every field from that one card, and write the ID next to the column heading. If you need to show a field in another unit, convert only the value from that same card, using the conversion definitions supplied with the dataset, and keep the original number and unit visible beside the converted one. Only fields with a recorded unit can be converted; maximum_power_hp and engine_capacity have none. This is a method, not a ranking: nothing here shows that one variant is better than another.

Missing values and scope

A null value means not provided, never zero. clearance_max is empty on all six records. fuel_consumption_mixed is empty on 49798, 49799, 49802 and 49803. Do not fill these gaps with values from a sibling record that has the same name; that is exactly the mixing this guide warns against. The unit l on the consumption fields does not say what distance the figure refers to, so no per-distance unit such as l/100 km is claimed.

Scope limits: the manufacturer has not verified these records. They include no prices, and they are not claimed to apply to every model year or market. They support no reliability claims, overall winner or purchase recommendation.

Source provenance

All figures come from the park-knowledge source collection, dataset toyota-4runner-generation-5359. They are drawn from modification records 49798, 49799, 49800, 49801, 49802 and 49803 (generation 5359, batch 1), captured on 2026-09-28. Frozen snapshot SHA256: 9e1e0bd75119e84b791409e40c1730c88bfd4c9c3a602e11332d315788f4292f. The figures have not been checked against any current external source. No public URL is cited because none came with the evidence. When you reuse a figure, cite its record ID and the capture date with it.