Methodology

Where the data comes from

Our directory is built from public RTO code lists: the two letter state and union territory codes and the Regional Transport Office district numbers that make up an Indian number plate. We compile 1,316 RTO codes across 35 states and union territories, each with its registering city and, where known, the office name and jurisdiction. Roughly 1,185 codes also carry an approximate map location for the RTO district.

How the decoder works

When you enter a plate, the decoder reads the leading RTO code: the first two letters plus the following one or two digits, for example RJ14 from RJ14UD5810. It looks that code up in our directory and returns the matching RTO office, city and state. If a code is not in our records, we say so plainly rather than guess. The lookup runs in your browser against a small reference file; we do not send the plate you type to any server.

What we deliberately do not show

We decode the place a vehicle is registered, never the person. We do not show, fetch or store any owner personal details: no name, address, phone number, chassis or engine number. That data is private and protected, and surfacing it would be wrong. For limited official record details, use the government mParivahan app or the VAHAN portal, as described in our how to check guide.

Accuracy and refresh

RTO records change: new district offices open and jurisdictions get redrawn. Our data is indicative, not official, and we refresh it periodically against public sources. Always verify anything important with the RTO or Parivahan.

Report a correction

If a code, city or office looks wrong, tell us and we will check it. You can also write to corrections@vehicledetails.in.