UA Vehicle Registry — Enhanced Quality
Normalized and data-quality enhanced derivative of the Ukrainian open dataset on registered vehicles, published by the Ministry of Internal Affairs.
info About the dataset
UA Vehicle Registry — Enhanced Quality is a derivative dataset built from the official open vehicle registry of the Ministry of Internal Affairs of Ukraine. The original data is published on data.gov.ua.
The original dataset has numerous quality issues: mixed encodings (Windows-1251 / UTF-8), unstable schema (different column names across months), massive duplicates (~85%), and lack of brand/model normalization.
We fix these issues with an automated data quality pipeline and publish clean, analysis-ready snapshots in Parquet and CSV formats.
verified Quality Improvements
Encoding
Automatic encoding detection (Windows-1251, UTF-8, KOI8-U) and conversion to unified UTF-8.
Schema Stabilization
Unification of column names from different months into a single stable schema.
Deduplication
Removal of ~85% duplicates. The original dataset contains repeated records for each month.
Type Casting
Dates, numeric fields, categorical variables — cast to correct data types.
Brand/Model Normalization
Fixing typos, unifying spelling, mapping to standardized brand and model names.
Parquet Format
Columnar format for efficient analytical queries. ~10x compression compared to CSV.
source Source
Information on vehicles and their owners
Ministry of Internal Affairs of Ukraine
table_chart Data Schema
Complete list of columns in the dataset (v2.0). Extended fields are available via API.
| # | Column | Type | Example | Description |
|---|---|---|---|---|
| 1 | record_id | VARCHAR | d6179fa48a159e3c… | Unique record identifier (SHA-256 hash) |
| 2 | person | VARCHAR | P | Owner classification: P (natural person) or J (legal entity) |
| 3 | reg_addr_koatuu | VARCHAR | 8036100000 | KOATUU code of the owner's registered address |
| 4 | oper_code | INT | 40 | Registration operation numeric identifier |
| 5 | oper_name | VARCHAR | ВТОРИННА РЕЄСТРАЦІЯ ТЗ… | Full registration operation name |
| 6 | oper_car_condition | VARCHAR | used | Vehicle condition at operation |
| 7 | short_oper_name | VARCHAR | Вторинна реєстрація | Short operation name |
| 8 | oper_description | VARCHAR | Купив вживане авто… | Human-readable operation description |
| 9 | oper_notes | VARCHAR | Людина купила вживане… | Additional operation notes |
| 10 | owner_change | INT | 1 | Whether ownership changed (1/0) |
| 11 | is_import | INT | 0 | Whether the operation is a vehicle import (1/0) |
| 12 | is_aid | INT | 0 | Whether related to humanitarian aid (1/0) |
| 13 | is_credit_leasing | INT | 0 | Whether credit/leasing is involved (1/0) |
| 14 | modification_type | VARCHAR | — | Modification type |
| 15 | document_basis | VARCHAR | purchase_contract | Document basis (purchase_contract, etc.) |
| 16 | entity_type | VARCHAR | any | Operation entity type |
| 17 | is_wartime | INT | 0 | Whether performed during wartime (1/0) |
| 18 | is_digital | INT | 0 | Whether it is a digital operation (1/0) |
| 19 | is_stolen_related | INT | 0 | Whether related to theft (1/0) |
| 20 | is_insurer | INT | 0 | Whether the entity is an insurer (1/0) |
| 21 | is_social | INT | 0 | Whether it is a social operation (1/0) |
| 22 | d_reg | DATE | 2021-06-15 | Date of the registration operation (YYYY-MM-DD) |
| 23 | dep_code | VARCHAR | 1330313 | Service center identifier |
| 24 | dep | VARCHAR | ТСЦ 1330 | Service center name |
| 25 | dep_region | VARCHAR | Харківська | Service center region |
| 26 | dep_city | VARCHAR | Харків | Service center city |
| 27 | dep_address | VARCHAR | вул. Клочківська | Service center address |
| 28 | dep_address_number | VARCHAR | 228 | Service center building number |
| 29 | dep_description | VARCHAR | Реєстрація ТЗ, техогляд | Service center description |
| 30 | dep_hours_of_work | VARCHAR | Пн-Пт 09:00-18:00 | Service center working hours |
| 31 | dep_phones | VARCHAR | +380577001234 | Service center phone numbers |
| 32 | brand | VARCHAR | Toyota | Vehicle brand (Latin) |
| 33 | model | VARCHAR | Camry | Vehicle model (Latin) |
| 34 | generation | LIST<VARCHAR> | ["XV70 facelift 2017"] | Model generation |
| 35 | model_suffix | VARCHAR | XLE | Model suffix |
| 36 | make_year | INT | 2021 | Manufacturing year |
| 37 | model_year | INT | 2021 | Model year (may differ from manufacturing year) |
| 38 | vin_year_code | VARCHAR | M | Year code from VIN (10th position) |
| 39 | color | VARCHAR | Сірий | Vehicle body color |
| 40 | kind | VARCHAR | Легковий | Vehicle category (passenger, cargo, etc.) |
| 41 | body | VARCHAR | Седан | Body style (sedan, hatchback, etc.) |
| 42 | possible_body_types | LIST<VARCHAR> | ["Sedan"] | Possible body types for the model |
| 43 | body_subtype | VARCHAR | 4-door | Body subtype |
| 44 | body_modifiers | VARCHAR | — | Body modifiers |
| 45 | vehicle_class | VARCHAR | — | Vehicle class (A, B, C, D, ...) |
| 46 | trailer_prefix | VARCHAR | — | Trailer prefix |
| 47 | purpose | VARCHAR | Загальний | Vehicle intended use |
| 48 | fuel | VARCHAR | Бензин | Primary fuel type |
| 49 | secondary_fuel | VARCHAR | Електро | Secondary fuel |
| 50 | is_gbo | INT | 0 | Whether LPG/CNG is installed (1/0) |
| 51 | is_hybrid | INT | 1 | Whether it is a hybrid (1/0) |
| 52 | fuel_notes | VARCHAR | Бензин + Електро | Fuel notes |
| 53 | possible_fuels | LIST<VARCHAR> | ["Petrol", "Hybrid"] | Possible fuel types for the model |
| 54 | capacity | INT | 2487 | Engine displacement (cm³) |
| 55 | power_kwt | INT | 110 | Engine power (kW). Present in the source from 2026-05; carried onto earlier registrations by VIN. |
| 56 | possible_displacements | LIST<INT> | [2487, 1998] | Possible engine displacements for the model (cm³) |
| 57 | own_weight | INT | 1570 | Curb weight (kg) |
| 58 | total_weight | INT | 2070 | Gross weight (kg) |
| 59 | payload | INT | 500 | Payload capacity (kg) |
| 60 | n_reg_new_cyrillic | VARCHAR | АХ4521ВР | Registration plate number (Cyrillic) |
| 61 | n_reg_latin | VARCHAR | AX4521BP | Registration plate transliterated to Latin |
| 62 | has_old_cyrillic | INT | 0 | Whether it has a Soviet-era license plate (1/0) |
| 63 | plate_type | VARCHAR | UA_MODERN | Plate type (UA_MODERN, etc.) |
| 64 | region_code | VARCHAR | AX | Region code from plate number |
| 65 | is_valid_plate | BOOLEAN | true | Plate format validation result |
| 66 | validation_error | VARCHAR | — | Plate validation error description |
| 67 | region_name | VARCHAR | Харківська | Region name by plate code |
| 68 | needs_moderation | BOOLEAN | false | Whether moderation is needed |
| 69 | raw_vin | VARCHAR | JTDKN3DU5M1234567 | Original VIN from source |
| 70 | vin | VARCHAR | JTDKN3DU5M1234567 | Normalized VIN code |
| 71 | is_valid_vin | BOOLEAN | true | VIN validation result |
| 72 | vin_validation_error | VARCHAR | — | VIN validation error description |
| 73 | vin_length | INT | 17 | VIN code length |
| 74 | vin_is_17 | BOOLEAN | true | Whether VIN has standard 17-character length |
| 75 | vin_has_ioq | BOOLEAN | false | Whether VIN contains forbidden characters I, O, Q |
| 76 | vin_wmi | VARCHAR | JTD | WMI code (first 3 VIN characters) |
| 77 | vin_wmi_manufacturer | VARCHAR | Toyota Motor Corporation | Manufacturer by WMI code |
| 78 | vin_wmi_region | VARCHAR | Asia | Manufacturer region by WMI code |
| 79 | vin_wmi_known | BOOLEAN | true | Whether WMI code is known in the manufacturer database |
| 80 | possible_transmissions | LIST<VARCHAR> | ["automatic", "manual"] | Possible transmission types for the model |
| 81 | possible_drives | LIST<VARCHAR> | ["Front wheel drive"] | Possible drive types for the model |
| 82 | backfill_confidence | VARCHAR | HIGH | Confidence level of recovered VIN for 2013–2020 records |
| 83 | backfill_stage | VARCHAR | stg1 | Pipeline stage at which VIN was recovered |
| 84 | source_schema_version | VARCHAR | v2_17col | Schema version of the source MVS file: empty — legacy (before 2026-05), v2_17col — current. |
Schema v2.0 — 84 fields. Includes extended operation info, service centers, VIN analysis, body/fuel characteristics, and backfill metadata.
api API Access
REST API for programmatic access to data with extended fields. First 1,000 requests are free.
Vehicle Registry — Request Packages
Credits valid for 12 months from purchase. Field selection discussed individually. API keys are personal and non-transferable.
Additional APIs
Separate endpoints for quick search and verification. Can be combined with registry packages or purchased separately.
Plate ↔ VIN Lookup
Find VIN by license plate or license plate by VIN. Current and historical records.
Vehicle History
Full vehicle registration history by VIN or license plate: ownership changes, regions, dates. Online marketplace listings.
VIN Decode
VIN decoding: manufacturer, model, year, body type, engine, country and assembly plant. Pay only for successful decodes.
Annual Subscriptions
Fixed price, unlimited requests, full data access. Price depends on the number of extended fields.
1-Year Subscription
For regular analytics and integrations
- checkUnlimited requests
- checkBulk export (Parquet / CSV)
- checkMonthly data updates
- checkTechnical support
- checkData processing & analysis recommendations
5-Year Subscription
Best value for long-term projects
- checkUnlimited requests
- checkBulk export (Parquet / CSV)
- checkMonthly data updates
- checkPrice lock guarantee
- checkMCP Server included free
- checkData processing & analysis recommendations
AUTOMOTO MCP Server
Connect AI assistants (Claude, ChatGPT, Cursor) directly to registry data via Model Context Protocol. Available for Business/Enterprise plans or as a separate add-on.
open_in_new MCP GatewayAPI keys and downloaded data are personal and may not be transferred, resold, or shared with third parties. Violation of terms results in access termination without refund.
All prices are exclusive of VAT. For custom solutions — contact us.
table_chart Extended Fields
From 27 free base fields to 80+ extended with VIN decoding, technical specs, and EU data.
lock_open Open Data (free)
~27 fieldsAll data from the Ukrainian MIA database — normalized, deduplicated, and quality-enhanced. VIN codes included only where present in the original dataset.
- Registration number
- Make / model (normalized)
- Year of manufacture
- Color
- Fuel type (raw)
- Engine capacity
- Own / total weight
- Registration date
- Operation code
- KOATUU code
verified Basic
~30 fields+ on top of base:
- Corrected body type
- Corrected fuel type
- Corrected drive type
- KATOTTG (new classifier)
- VIN validation
- VIN error correction
- KOATUU decoded name
- Service center address
star Standard
~50 fields+ on top of Basic:
- Vehicle modification
- Generation
- Basic VIN decoding (NHTSA)
- Transmission type
- Horsepower / kW
- Euro emission class
- Additional tech specs
diamond Pro
80+ fields+ on top of Standard:
- Full VIN decoding
- European vehicle decoding
- Extended technical specs
- Country of manufacture + plant
- All analytical tools
- 5 custom analytical reports/year
- Priority support & consulting
- MCP Server access
- Recovered VINs for 2013–2020 records
bug_report Known Issues
12 categories of issues in the original MIA dataset (~46.8 GB, 146 CSV files), identified and fixed in the Enhanced Quality version.
невизначено, spaces, dashes, NULLdescription Documentation & Links
Data Schema
Description of all columns, data types, and allowed values.
Quality Report
12 categories of source data issues and remediation methods.
DQ Reports
Detailed quality reports for each monthly and annual data snapshot.
README
Full project description, usage instructions, and examples.
Releases
All dataset versions available for download.
License
CC BY 4.0 — free use with mandatory attribution.
person Author
format_quote How to Cite
Klimnyk, M. (2026). UA Vehicle Registry — Enhanced Quality. https://doi.org/10.5281/zenodo.19099441When using this data, you must credit Mykhailo Klimnyk and AUTOMOTO.AI as authors of the enhanced version, and MIA Ukraine as the source of the original data.
apps Other AUTOMOTO Products
Ready to work with the data?
Download the free dataset or contact us for custom solutions.
FAQ
It is a derivative dataset built from the official open vehicle registry of the Ministry of Internal Affairs of Ukraine. We fix encoding issues, stabilize schema, remove ~85% duplicates, normalize brands and models, and publish clean data in Parquet and CSV.
The dataset contains ~24 million unique vehicle registration records covering 2013–2026. The original MIA dataset contains significantly more due to massive duplicates, which we remove.
The free Open Data set contains 27 base fields (plate, make, model, year, color, etc.). Paid tiers add corrected body/fuel types, VIN validation, VIN decoding, vehicle generation, horsepower, Euro class, and up to 80+ fields total.
The API works on credits or annual subscriptions. First 1,000 requests are free. You can purchase packages from 10K to 200K requests, or an annual subscription with unlimited requests. Additional APIs include plate/VIN lookup, vehicle history, and VIN decoding.
The free dataset includes VIN codes only where present in the original MIA data. Paid tiers add recovered VIN codes for 2013–2020 records (missing from the original), VIN validation, error correction, and full decoding.
Yes, via AUTOMOTO MCP Server you can connect Claude, ChatGPT, Cursor and other AI assistants directly to registry data via Model Context Protocol. MCP Server is available for Business/Enterprise plans or as a separate add-on.
