Main SQL tables
car_make |
Makes |
car_model |
Models |
car_generation |
Generations |
car_serie |
Series |
car_trim |
Trims |
car_equipment |
Equipments |
car_specification |
Specifications |
car_specification_value |
Specification values |
car_option |
Options |
car_option_value |
Option values |
car_type |
Vehicle types |
year |
Years |
These are the actual table names shipped in the dump. Screenshots of each table are on the main page.
Database contents example
General information
| Number of doors | 5 |
| Country | Germany |
| Car class | C |
| Steering wheel position | Left |
Chassis
| Body type | |
| Number of seater | 5 |
| Length | 4703 mm |
| Width | 1826 mm |
| Height | 1436 mm |
| Wheelbase | 2808 mm |
| Track front | 1564 mm |
| Track back | 1551 mm |
| Ground clearance | 130 mm |
| Clearance | 165 mm |
| Curb weight | 1905 kg |
| Wheel size | 205/50/R15 |
| Full weight | 2520 kg |
| Capacity | 615 kg |
| Front/rear axle load | - kg |
| Cargo compartment (Length x Width x Height) | 0 x 0 x 0 mm |
| Cargo compartment volume | 0 m3 |
| Min trunk capacity | 520 l |
| Max trunk capacity | 520 l |
| Loading height | 690 mm |
| Trailer load (with brakes) | 4820 kg |
| Disc size | 8.0jx17 |
| Pitch Circle Diameter | DIA67.1 5x114.3 mm |
Engine
| Engine type | |
| Engine model | SPJD |
| Engine placement | front, longitudinal |
| Capacity | 2995 cm3 |
| Power output | 180 hp |
| Max power (kW) | 60 kW |
| Max power at RPM | from 5 200 to 6 500 RPM |
| Maximum torque | 440 N*m |
| Turnover of maximum torque | from 2 900 to 4 750 RPM |
| Injection type | Direct injection |
| Boost type | Compressor |
| Presence of intercooler | Present |
| Engine configuration | V-shaped |
| Number of cylinders | 4 |
| Valves per cylinder | 4 |
| Cylinder bore | 82 mm |
| Stroke cycle | 89 mm |
| Compression ratio | 10,8 |
| Timing belt | DOHC |
| Flow calculation method | NEDC |
Gearbox and handling
| Gearbox type | |
| Number of speed | 8 |
| Drive wheels | |
| Turning circle | 12.3 m |
Suspension and brakes
| Front suspension | Independent, Pneumatic, Multilink, with Stabilizer bar |
| Back suspension | Independent, trapezoidal link |
| Front brakes | Ventilated disc |
| Rear brakes | Ventilated disc |
Operating characteristics
| Max speed | 250 km/h |
| Acceleration (0-100 km/h) | 5.7 s |
| City driving fuel consumption per 100 km | 9 l |
| Highway driving fuel consumption per 100 km | 5,2 l |
| Mixed driving fuel consumption per 100 km | 6,6 l |
| Fuel tank capacity | 65 l |
| Cruising range | from 780 to 1 300 km |
| Fuel | 95 |
| Emission standards | EURO IV |
| CO2 emissions | 107 g/km |
Safety
| Safety assessment | 2 / 4 |
| Rating name | EuroNCAP |
Accumulator battery
| Battery capacity | 12 KW⋅h |
| Electric power reserve | 150 km |
| Charging time | 60 h |
| Battery type | Lithium-ion (Li-ion) |
| Battery temperature | -25-50 C |
| Fast charge time | 40 h |
| Description of fast charging | Up to 80% at 50 kW |
| Charging connector type | GBT_AC |
| Consumption | 13.5 KW⋅h/100 km |
| Maximum charging power | 50.0 KW |
| Battery capacity (available) | 16.4 KW⋅h |
| Number of charging cycles | 1500 |
Example shows what information about the specific trim is stored in the car database.
How values and translations work
Specifications are normalized: one table is a dictionary of field names, and another stores the actual value for each trim as a separate row. Every record has a stable numeric ID and creation/update timestamps, so you can track what changed and when.
The same underlying IDs are shared across all language editions of Car2DB — a record for a given trim resolves to the same specifications whichever language database you query. The database is refreshed monthly.
Field coverage depends on the specific make, model, generation and market: not every trim has a value for every field.
Formats and use cases
MySQL & CSV
Full relational dump — best for importing into your own database or data pipeline. Pricing →
Excel (XLSX)
The same makes, models and specifications in one spreadsheet — no database required. Excel →
REST API & MCP
Live lookups for applications and AI agents, with an MCP server for AI assistants. API →
How the data is organized
Technical specifications and equipment options are attached at the trim level — the same modification can appear with different values across body styles or markets.
FAQ
Is every field filled in for every vehicle?
No. Field coverage depends on the make, model, generation and data source — some trims have detailed specifications, others only the core fields.
How often is the data updated?
The database is regenerated monthly; see the actuality date on the main page.
In which formats can I get the data?
A MySQL dump and CSV come with every purchase; other formats are listed above.
Which languages are available?
Car2DB ships in 11 languages; this page describes the edition sold on this website.
