Texas RRC District, County, and Field Codes: A Source-Label Crosswalk

Direct answer for mineral owners

Keep the RRC district code, RRC county code, eight-digit field number, field name, and any page-specific FIPS code in separate source-labeled fields. Copy each value exactly as shown with its dataset or screen, field class, and access date. None of these labels alone proves a field boundary, well or lease connection, private ownership, production, reserves, or value.

Key takeaways for mineral owners

• An RRC district code labels a Commission administrative region; it is not a county code or field boundary.
• The RRC field number is an eight-digit source field with a five-digit field portion and three-digit reservoir portion.
• Field name and field number are separate labels, and associated field records may use different numbers.
• Preserve RRC county code and page-specific FIPS code under the exact labels the source displays.
• A field may span districts or counties, so one code does not prove a complete field or private-property relationship.

Source-label crosswalk, not a property conclusion. This page explains how selected Texas Railroad Commission labels differ. It does not identify a field boundary, well, lease, tract, unit, owner, title interest, royalty account, production result, reserve, 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: an RRC district code, RRC county code, eight-digit field number, field name, and a page-specific FIPS code are distinct source labels. Keep each in its own column. Copy the value exactly as shown, retain its source page or dataset, identify the field class, preserve leading characters, and record the access date.

Do not create one generic location code or field code column. A source label can organize a controlled search, but it does not by itself prove where a field ends, which well or lease belongs to a private interest, who owns minerals, whether production is complete, or what an interest is worth.

The source-label crosswalk

Label lane	Source-owned role	Preserve beside it	What it does not establish
RRC district code	Commission administrative-region label	Exact district code, district name or office when shown, source object, access date	County identity, field boundary, tract, title, ownership, or value
RRC county code	County field inside the named RRC data object	Exact field label, code as shown, county name when shown, file or screen, access date	That it equals a FIPS code or covers every county associated with a field
Eight-digit field number	RRC field-and-reservoir identifier	All eight digits, field class, field name, district and county context when present	Field geometry, well or lease connection, private ownership, reserves, or value
Field name	Separate RRC text field	Exact spelling and punctuation, associated field number, source version, access date	That similar names share one number, reservoir, boundary, or private interest
Source-page FIPS code	Value displayed under a FIPS Code heading on the named page	Exact page title, exact heading, county row, access date	Automatic equivalence to an RRC county-code field in another dataset

A strong reusable row also includes source owner, source object, exact label, controlled value reference, field class, copied by, copied at, format preserved, and question not answered. Keep real identifiers and owner records in an authorized controlled location; a public blank template should not expose them.

District code is an administrative-region label

The RRC Field Information manual explains that the Commission created districts as administrative regions. It lists the district labels used for oil and gas records and explains that a field can lie in one district or span more than one district.

That makes the first stop condition important: a district code is not a field outline. It does not say that every well in the district belongs to one field, that a field remains inside one district, or that a private tract participates in any field.

The current Oil and Gas Counties and Districts page displays separate columns for County, District Code, FIPS Code, and District Office. Preserve those headings as the page presents them. A district office name supplies administrative context; it is not another identifier for a well, lease, field, or mineral owner.

Use a district-code row like this:

Crosswalk field	Entry rule
Exact label	Copy District Code when that is the displayed heading
Controlled value	Preserve all characters in the authorized record
District context	Retain district name or office only when the source displays it
Source object	Record the exact page, table, data file, or screen
Access date	Record retrieval time separately from any record period
Stop note	Administrative region; not a field or property boundary

County code and page-specific FIPS code stay separate

The RRC’s Data Sets Available for Download catalog describes Oil & Gas Field Name & Numbers records as containing district, field number, county code, and field name. Those are separately named elements in that data family.

The counties-and-districts page, by contrast, uses the heading FIPS Code. This article does not assume that a value under that heading can be copied into a field named County Code in another RRC file. Instead, retain the exact source label and dataset or page. If a later data dictionary explicitly documents a conversion, record the conversion rule, responsible source, version, and date in a separate field.

This prevents a common evidence problem: a spreadsheet may contain a plausible-looking county value but no indication of whether it came from a Commission data-file field, a page-specific FIPS column, a county name, or a user-created abbreviation. Without that provenance, the value cannot safely carry the meaning of any one source field.

The eight-digit field number has two source-defined portions

The RRC Field Information manual defines the field number as eight digits. It describes the first five digits as the unique field portion and the last three digits as the reservoir portion. Preserve all eight digits, including leading zeroes, in a text-formatted field.

Do not convert the value to an ordinary spreadsheet number. Numeric conversion can remove leading zeroes, apply scientific notation, or encourage someone to split the value without keeping the official field definition. If analysis needs the two portions, preserve the original eight-digit value and create separately labeled derived fields with the source rule and transformation date.

The number identifies an RRC record lane. It does not define the field’s geographic boundary, prove that a well or lease belongs to the field, show that a private mineral interest participates, or establish production, reserves, future development, or value.

For the actual query attempt and result state, use the Texas RRC Field Search Retrieval Provenance Worksheet. That page owns query execution. This crosswalk owns only the labels that a retained source displays.

Field name is not a substitute for field number

The Field Information manual defines the field name separately from the field number and describes oil and gas field classifications. It also documents associated fields and notes that associated records can use different field numbers. That is enough to reject a name-only join.

Preserve the field name exactly as displayed, including spacing and punctuation. Keep the corresponding field number, field class, source file or screen, version or effective context when supplied, and access date in separate columns. If two names look similar, record a comparison question instead of overwriting one with the other.

Name similarity does not prove a shared reservoir, boundary, well set, lease, operator, owner, or private-property relationship. Those conclusions require their responsible sources and, where appropriate, qualified technical or title review.

One field can span districts or counties

The manual says a field may be located within one district or may span districts. Its gas-field record descriptions also allow county-code occurrences for multiple counties. A single district or county value therefore should not be presented as the complete geography of every field.

This does not mean every field spans multiple regions. It means the crosswalk must retain the source’s occurrence and file structure rather than forcing every field into one district or one county cell. If a source supports multiple rows, preserve the repeated rows with the same field-number reference and the source-specific occurrence order.

Do not draw a field polygon, allocate acreage, assign a well or lease, or make an ownership conclusion from this list. A district or county association is regulatory record context, not a private title opinion.

Keep co-displayed labels from becoming false joins

The current Oil Leases and Gas Wells by District and Operator page describes a monthly index organized by district, operator name, and lease name. It says the index includes operator number, lease number, field number and name, county number and name, and an oil-or-gas label.

That co-display is useful because it tells a records organizer which companion labels to retain. It does not make an operator number a field number, a county number a district code, or a lease name a field name. It also does not prove that a row applies to an owner’s deed, tract, unit, royalty account, or payment history.

For cross-system identifier roles, use CAD Account Number, RRC Lease ID, and Operator Number in Texas Mineral Records. Article 298 owns the CAD, API, district-plus-lease or gas-well, and P-5 distinctions. This page does not repeat them.

A blank crosswalk for a controlled packet

Packet column	Entry rule	Stop condition
Source owner	Record Texas RRC or the actual issuing body	Stop if the issuer is unclear
Source object	Exact page, manual, dataset, file, or query-result screen	Do not cite a cropped label without its source
Exact field label	Copy the heading as displayed	Do not normalize District Code, County Code, and FIPS Code into one label
Controlled value reference	Point to the authorized record without exposing it publicly	Never publish real identifiers in the reusable template
Field class	District, RRC county, field number, field name, page FIPS, or other	Stop if the class is only guessed
Companion context	Name, office, field class, oil-or-gas lane, version, or occurrence when shown	Do not detach a value from source context
Format preserved	Confirm leading characters and punctuation were retained	Do not allow spreadsheet numeric coercion
Access date	Date, time, and timezone of retrieval	Do not call access time the record’s effective date
Question not answered	State the boundary in plain language	Stop before inferring a field, asset, ownership, production, or value conclusion

For a broader production-search index, use How to Build a Texas Mineral Production Record Locator Sheet. It owns search organization across production sources. This article does not reproduce its locator fields.

What the crosswalk does not prove

No label in this crosswalk independently establishes:

• a field boundary, reservoir extent, acreage allocation, or engineering interpretation;
• that a well or lease belongs to a field, tract, unit, deed, or private mineral interest;
• title, mineral ownership, authority, royalty entitlement, or payment responsibility;
• production completeness, forecast, reserves, decline, or future activity;
• tax treatment, appraisal result, private value, offer quality, or buyer qualification; or
• that two records describe the same asset because a code, field name, county, district, lease name, or operator appears similar.

The crosswalk improves labeling and retrieval provenance. It does not expand what the underlying source proves.

Controlled source record

Five official source objects were retrieved on August 31, 2026 and retained as 1,647,508 controlled bytes.

Source object	Bytes	SHA-256 prefix	Role
RRC Data Sets Available for Download	114,876	ba615bbe5eeb	District, field number, county code, and field name labels
RRC Oil and Gas Counties and Districts	67,332	eb438c443e17	County, District Code, FIPS Code, and District Office headings
RRC Field Information manual	1,397,759	0c0a14e30b93	District, field-number, field-name, county-code, and file-key definitions
RRC Field Search	6,658	7b0c16b0c0b9	Current query surface and query-job boundary
RRC Leases and Wells by District and Operator	60,883	ea66a35fda29	Co-displayed district, field, county, operator, lease, and oil-or-gas context

Claim ledger and stop conditions

Claim ID	Supported statement	Allowed evidence label	Stop condition
C299-01	The field-name-and-number dataset names district, field number, county code, and field name separately	RRC-FIELD-DATA-LABEL	Do not collapse the labels or infer a property relationship
C299-02	The current county page displays District Code and FIPS Code in separate columns	RRC-PAGE-LABEL	Do not silently relabel a page FIPS value as another dataset’s county code
C299-03	RRC districts are administrative regions, and a field can span districts	RRC-DISTRICT-GEOGRAPHY	Do not present a district as a field boundary
C299-04	The eight-digit field number contains a five-digit field portion and three-digit reservoir portion	RRC-FIELD-NUMBER	Preserve all eight digits and do not infer geometry or ownership
C299-05	Field name is separate, and associated field records can use different field numbers	RRC-FIELD-NAME	Do not join records on name similarity alone
C299-06	Gas-field records can carry county-code occurrences for multiple counties	RRC-FIELD-COUNTY-OCCURRENCE	Do not force every field into one county or infer tract inclusion

Research scope and review boundaries

Before using these labels in an owner-specific decision, verify the exact source object, dataset or screen, field label, format, district and county context, field class, version, occurrence, access date, legal description, tract or unit evidence, ownership documents, and purpose. Questions about field boundaries, geology, engineering, title, tax, accounting, production, valuation, or a transaction belong with the responsible official source and qualified advisers.

Sources reviewed for this article

• Texas RRC: Data Sets Available for Download
• Texas RRC: Oil and Gas Counties and Districts
• Texas RRC: Field Information manual
• Texas RRC: Field Search
• Texas RRC: Oil Leases and Gas Wells by District and Operator

Related mineral-rights research guides

• Texas Mineral Rights Guide
• CAD Account Number, RRC Lease ID, and Operator Number in Texas Mineral Records
• Texas RRC Field Search Retrieval Provenance Worksheet
• How to Build a Texas Mineral Production Record Locator Sheet

Educational information only. This article explains source-owned regulatory labels and evidence boundaries. It is not legal, title, land, tax, appraisal, accounting, engineering, geological, investment, or financial advice; it is not a field delineation, 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 an RRC district code the same as a county code?

No. The RRC uses district codes for Commission administrative regions and displays county codes as separate source fields. Keep both exact labels when a record contains them.

How is an eight-digit Texas RRC field number structured?

The RRC Field Information manual describes an eight-digit number made from a unique five-digit field portion followed by a three-digit reservoir portion. Preserve all eight digits exactly as shown.

Is a field name interchangeable with its field number?

No. The RRC manual defines field name separately, and associated field records can use different field numbers. Preserve both fields rather than treating the name as the number.

Can one Texas oil or gas field span districts or counties?

Yes. The RRC manual says a field may be in one district or span districts and documents gas-field county-code occurrences for multiple counties. That does not establish a private tract or ownership connection.

Should a FIPS code be copied into an RRC county-code field?

Not without source-specific documentation. The current RRC counties-and-districts page displays District Code and FIPS Code in separate columns. Preserve the exact page label and source instead of silently relabeling the value.

Sources reviewed for this article

• Texas RRC Data Sets Available for Download (accessed 2026-08-31)
• Texas RRC Oil and Gas Counties and Districts (accessed 2026-08-31)
• Texas RRC Field Information manual (accessed 2026-08-31)
• Texas RRC Field Search (accessed 2026-08-31)
• Texas RRC Oil Leases and Gas Wells by District and Operator (accessed 2026-08-31)