OOBDPhone®
EN⌄
FrançaisEnglishDeutschItalianoEspañolNederlands (BE)
Buy on Amazon
Menu

Functions to test

Check your car’s OBD2 compatibility

Choose your model, year and engine. See the result and the engine functions concerned.

Documentary distribution of 657 records

29.7 %Supported OBD2 signal195 / 65761.5 %To confirm404 / 6578.8 %Not compatible / out of scope58 / 657

●A green signal does not guarantee OBDPhone on your exact engine. Hybrids, unknown powertrains and years outside the range automatically return to confirmation.

●France-focused database · documentary review 5 September 2026

OBDPhone®

Identify your vehicle

Choose your model, year and engine. See the result and the engine functions concerned.

Add the year and engine to help identify your version.

Select the model, year and engine to see compatibility information. Need help with the result? Contact our support team before choosing.

A transparent answer

The scope to verify.

These are intended product functions, not functions validated on every listed vehicle.

i

Functions to test

Engine and emissions

  • Read generic engine fault codes
  • Clear codes after repair
  • View available live engine data
  • Connect with Car Scanner on iOS and Android
Functions requiring a suitable specialist tool
  • Airbag, ABS and specialist control units
  • Coding, programming and workshop functions
  • Traction battery and advanced hybrid data
  • Advanced make-specific functions
Sources and checking method

Documented OBD2 observations and OBDPhone® tests are identified separately. The result explains what to check for your version.

Confidence made visible

Three different kinds of evidence.

Reliable vehicle characteristics do not prove OBDPhone operation.

01

Characteristics

Manufacturer source

Documents identity and powertrain, not historical model years or the exact diagnostic protocol.
02

Technical clue

Profile or external observation

Useful for planning a test. Another adapter or a Car Scanner profile does not validate OBDPhone.
03

Product validation

Exact test required

No traceable OBDPhone test is attached to the records in this release.

Our method

Sources with explicit limitations.

657 documentary records across 45 makes: 520 audited legacy records and 137 additions. These are not 657 vehicles declared compatible.

The previous 2,318 observations are inherited external counters, not OBDPhone tests. External records have not all been individually revalidated.

Historical production periods are not validated model years. Market, engine, adapter, firmware, phone and app must match a traceable test.

Does an OBD2-shaped port guarantee compatibility?+

No. The connector may be present while standard engine data is unavailable or limited.

What about hybrid and electric vehicles?+

A compatible hybrid is limited to the combustion engine and generic emissions. Fully electric vehicles are outside the standard OBDPhone® use case.

My vehicle is not listed+

Contact us with the make, model, year and fuel type so we can help check it.

Sources and evidence scope

These documents describe characteristics or technical guidance. They are not an OBDPhone test of your vehicle.

Sources and evidence scope+

Unsure about your version?

Have it checked before purchase.

Contact support →