MRX Learning Center
CAD Account Number, RRC Lease ID, and Operator Number in Texas Mineral Records
A CAD account number, API number, RRC lease or gas-well ID, district, and P-5 operator number identify different record objects and should not share one field.
Direct answer for mineral owners
Keep every identifier in a source-labeled field. A CAD long account number and short account or R-number identify property records in an appraisal-district system. An API number identifies an RRC wellbore. An RRC district plus oil lease number or gas-well ID identifies a completion or production lane, while a P-5 number identifies the operator. Similar numbers or names do not prove that two records describe the same private mineral interest.
Key takeaways for mineral owners
- A CAD long account number, short account or R-number, and GIS parcel ID can be different fields in the same local system.
- The RRC uses an API number for a wellbore and district plus oil lease number or gas-well ID for a completion or production lane.
- A P-5 number identifies an operator, not a mineral owner, tract, royalty account, or property connection.
- Copy each identifier exactly as shown, including its source, field label, oil-or-gas context, district, and retrieval date.
- Do not join records merely because numbers, lease names, operator names, counties, or fields look similar.
Identifier crosswalk, not a property-match conclusion. This page explains source-owned labels in Texas mineral records. It does not identify an owner, legal description, tract, unit, lease effect, royalty decimal, payment right, appraisal result, tax amount, production result, private value, offer, buyer action, or transaction outcome. MRX provides educational information and resources only and does not buy mineral rights.
The direct answer is: a CAD account number, an RRC API number, an RRC lease or gas-well identifier, and an RRC operator number belong to different record systems and answer different identity questions. Keep each value in its own field with the agency, exact source label, oil-or-gas context, district where shown, and retrieval date.
Do not turn one of these numbers into a universal property key. A similar number, lease name, operator name, county, or field can guide a controlled follow-up search, but it does not prove that two records describe the same private mineral interest.
The identifier crosswalk
| Identifier lane | Source-owned role | Fields to preserve beside it | What it does not prove |
|---|---|---|---|
| CAD long account number | Appraisal district’s long or geographic property code | District, exact field label, legal-description reference, tax year, retrieval date | Title, mineral ownership, account correctness, or private value |
| CAD short account or R-number | Appraisal district’s shorter local property code | Long account number when shown, district, exact format, retrieval date | That it equals a GIS ID, RRC number, or another district’s format |
| RRC API number | Regulatory wellbore identifier | County, district, well label, source route, retrieval date | Tract inclusion, lease effect, royalty entitlement, production, or value |
| RRC district plus oil lease number or gas-well ID | Regulatory completion or production-lane identifier | Oil-or-gas label, district, lease or well name, operator label, period | Private lease interpretation, owner participation, decimal, or payment |
| RRC P-5 operator number | Regulatory organization identifier | Operator name as displayed, status context, source route, retrieval date | Mineral ownership, authority for a private party, payee identity, or buyer qualification |
The safest reusable row also includes source object, copied by, copied at, format preserved, connection evidence, and question not answered. If the issuer or field label is unclear, stop before making a join.
CAD long account, short account, and GIS ID are separate fields
The current Texas Comptroller Electronic Appraisal Roll Submission manual defines its account-number field as the unique long code an appraisal district uses to identify a specific property. It notes that geographic account number and Geo ID can be other names for that long code. The manual separately defines the short account number as a unique short code that may also be called a parcel number or R-number.
The same manual has a separate GIS parcel ID field and says that value may or may not match the account or short account number. That is a useful stop condition: do not assume every local property identifier is an alias merely because the values appear on one screen.
The current Electronic Property Transaction Submission manual likewise calls the short account number a locally assigned shortened account or R-number. It says a separate record should be submitted for each account when a transaction includes more than one account. This article uses that statement only as support for preserving separate rows. It does not interpret a transaction or deed.
Use this CAD capture pattern:
- copy the district name and exact page, file, or report title;
- copy the label exactly: long account, geographic account, Geo ID, short account, parcel number, R-number, or GIS parcel ID;
- preserve leading characters and punctuation exactly as shown;
- record the tax year or source period separately from the retrieval date; and
- write
not showninstead of manufacturing an alias or cross-system match.
API number identifies the wellbore lane
The Texas RRC About Oil and Gas Data Queries page says a wellbore is assigned a number referred to as the API number. It also says a wellbore may contain one or more completions or may be a dry hole.
That distinction matters when a family packet contains an API number and a lease number. The API value identifies the wellbore in the Commission’s regulatory system. It does not, by itself, say that a particular mineral owner participates in the well, that a deed covers the tract or depths, that a royalty decimal is correct, or that production belongs to a private account.
Use Texas RRC Wellbore Query Retrieval-Provenance Worksheet for the query-specific retrieval path. Article 298 owns only the cross-system identifier labels and does not repeat the query controls or result-field inventory.
District and lease or well IDs identify different RRC lanes
The same RRC query guide says each completion is identified by a district number and an oil lease number or gas-well ID number. Preserve all three parts of that statement:
- whether the record is in the oil-lease or gas-well lane;
- the RRC district; and
- the oil lease number or gas-well ID exactly as displayed.
Dropping the district or oil-or-gas context can make a copied number look more universal than the source says it is. A lease name is also not a substitute for the numbered field. Names can resemble one another, change, or appear differently across records.
The RRC Oil Leases and Gas Wells by District and Operator index is organized by district, operator name, and lease name. The current page says the monthly index includes operator number, lease number, field number and name, county number and name, and an oil-or-gas label. Co-display helps preserve context; it does not make those fields interchangeable.
The RRC Production Data Query System FAQ provides one bounded bridge. It says an API number can be entered in the Wellbore Query to obtain lease information, including a lease number, and that the lease number can then be used to access PDQ. That is a documented lookup sequence, not proof of a private-property connection. The FAQ also describes PDQ as a monthly, revisable snapshot.
P-5 number identifies the operator lane
The RRC query guide says a regulated company files an Organization Report, Form P-5, and that the Commission issues a P-5 number unique to that operator. Preserve the displayed operator name, number, status context, exact source, and retrieval date together.
An operator number is not an owner number. It does not identify the mineral owner, royalty payee, purchaser, title holder, private contract party, or qualified buyer. An operator name appearing beside a lease or well record does not establish the operator’s authority for a private person or prove that the record applies to the interest being reviewed.
For time-separated operator evidence, use Mineral Rights Operator Name Change Log. That page owns historical name transitions. This page owns only the identifier type and source label.
Copy identifiers as shown without publishing private values
A reusable public template should remain blank. Keep real account numbers, API numbers, lease or gas-well IDs, operator numbers, owner names, addresses, legal descriptions, coordinates, payment details, and private documents in an authorized controlled location.
For each controlled row, preserve:
| Packet field | Entry rule | Stop condition |
|---|---|---|
| Source owner | Texas Comptroller, appraisal district, Texas RRC, or another named issuer | Stop if the issuer is unclear |
| Exact source object | Page title, PDF name, query route, report, or retained file | Do not cite an informal screenshot label as the source |
| Identifier label | Copy the field name exactly as displayed | Do not rewrite a short account as an RRC lease ID |
| Controlled value reference | Point to the authorized record without exposing the value publicly | Do not place real identifiers in a reusable example |
| Companion fields | District, oil-or-gas label, long/short form, operator label, period, or status when shown | Do not detach a number from source-owned context |
| Retrieval provenance | Date, time, timezone, URL, file hash, or controlled capture reference | Do not call retrieval time the source’s effective period |
| Connection evidence | Separate deed, owner, tract, unit, payor, or title evidence when actually available | A matching number or name is not connection evidence by itself |
| Limitation | State the question the source does not answer | Stop before extending the record beyond its lane |
For a dedicated production-search index, use How to Build a Texas Mineral Production Record Locator Sheet. It owns the production-locator job; this article does not reproduce it.
What these identifiers do not establish
No identifier in this crosswalk independently proves:
- legal title, mineral ownership, authority, or the right to act;
- a legal description, tract, depth, unit, or private lease connection;
- that a CAD account is correct, current, or limited to a mineral interest;
- that an owner participates in a well or production record;
- a royalty decimal, payor obligation, payment amount, or entitlement;
- production completeness, engineering conclusions, reserves, or future activity;
- an appraisal result, tax result, private value, fair offer, or transaction outcome; or
- that two records describe the same property because their names or numbers resemble one another.
Those conclusions require their own responsible sources and qualified review. An identifier improves retrieval and provenance; it does not expand what a record proves.
Controlled source record
Five official source objects were retrieved on August 31, 2026 and retained as 9,528,232 controlled bytes.
| Source object | Bytes | SHA-256 prefix | Role |
|---|---|---|---|
| RRC About Oil and Gas Data Queries | 46,685 | 93b8dabdfa94 | API, lease or gas-well, district, and P-5 roles |
| RRC District and Operator Index | 60,883 | ea66a35fda29 | Co-displayed identifier context |
| RRC PDQ FAQ | 58,425 | 9efdfe4160a1 | Bounded API-to-lease lookup sequence |
| Comptroller Appraisal Roll Manual | 7,610,716 | e93aa72cb71f | Long, short, R-number, parcel, and GIS-ID boundaries |
| Comptroller Property Transaction Manual | 1,751,523 | 4ce4418f86f1 | Locally assigned short-account and separate-record rule |
Claim ledger and stop conditions
| Claim ID | Supported statement | Allowed evidence label | Stop condition |
|---|---|---|---|
C298-01 | CAD long and short account identifiers are separate source fields | CAD-ACCOUNT-FIELD | Do not treat either as an RRC identifier or title proof |
C298-02 | A CAD short account may be called a parcel number or R-number | CAD-SHORT-ACCOUNT | Do not assume a GIS parcel ID is identical |
C298-03 | An API number identifies an RRC wellbore | RRC-WELLBORE-ID | Do not infer owner participation or tract inclusion |
C298-04 | District plus oil lease number or gas-well ID identifies a completion lane | RRC-COMPLETION-ID | Do not drop district or oil-or-gas context |
C298-05 | A P-5 number is unique to an RRC operator | RRC-OPERATOR-ID | Do not call it an owner, payee, or buyer identifier |
C298-06 | API information can support a bounded lookup to lease information | RRC-LOOKUP-SEQUENCE | Do not present the sequence as private-property connection proof |
Research scope and review boundaries
Before joining records for an owner-specific decision, verify the source object, exact identifier label and format, district, oil-or-gas lane, period, version, operator context, legal description, tract or unit evidence, ownership documents, and purpose. If the question concerns title, appraisal, tax, accounting, production, valuation, or a transaction, use the responsible official office and qualified advisers.Sources reviewed for this article
- Texas RRC: About Oil and Gas Data Queries
- Texas RRC: Oil Leases and Gas Wells by District and Operator
- Texas RRC: Production Data Query System FAQs
- Texas Comptroller: Electronic Appraisal Roll Submission Manual
- Texas Comptroller: Electronic Property Transaction Submission Manual
Related mineral-rights research guides
- Texas Mineral Rights Guide
- Tax Year, Production Month, and Download Date in Texas Mineral Records
- How to Build a Texas Mineral Production Record Locator Sheet
- Texas RRC Wellbore Query Retrieval-Provenance Worksheet
Educational information only. This article explains source-owned identifier labels and evidence boundaries. It is not legal, title, land, tax, appraisal, accounting, engineering, geological, investment, or financial advice; it is not a property match, ownership opinion, production conclusion, valuation, offer, or transaction recommendation. Verify owner-specific facts with the responsible office and qualified advisers. MRX provides educational information and resources only and does not buy mineral rights.
Frequently asked questions
Is a CAD account number the same as an RRC lease ID?
No. A CAD account number belongs to a local appraisal-district property record. An RRC lease or gas-well identifier belongs to a Commission regulatory record and should retain its district and oil-or-gas context.
Is a CAD short account number always the same as its long account number?
No. The Comptroller manuals treat the long or geographic account number and the short account or R-number as separate fields. A GIS parcel ID may also differ.
What does an API number identify in Texas RRC records?
The Texas RRC describes the API number as the number assigned to a wellbore. It does not by itself prove ownership, tract inclusion, royalty entitlement, production, or value.
Why keep the RRC district beside an oil lease number or gas-well ID?
The RRC describes a completion using the district plus oil lease number or gas-well ID. Preserve the oil-or-gas label and district instead of treating the number as a universal property key.
Does a P-5 number identify a mineral owner?
No. The RRC says the P-5 number is unique to an operator. It does not identify the mineral owner, payee, tract, title chain, royalty decimal, or private transaction party.
Sources reviewed for this article
- Texas RRC About Oil and Gas Data Queries (accessed 2026-08-31)
- Texas RRC Oil Leases and Gas Wells by District and Operator (accessed 2026-08-31)
- Texas RRC Production Data Query System FAQs (accessed 2026-08-31)
- Texas Comptroller Electronic Appraisal Roll Submission Manual (accessed 2026-08-31)
- Texas Comptroller Electronic Property Transaction Submission Manual (accessed 2026-08-31)
A practical next step
Put your mineral rights in context.
Every mineral interest, royalty history, and written offer is different. Start with a question, or share what you have for a free underwriter review.
- Free
- Confidential
- No obligation to sell
Ready for a closer look?
Open the Texas Mineral Rights GuideGet a directional range with the assumptions clearly stated.