Wellbore Well Identifiers
Queryable Fixed-width
The oil lease and well numbers a wellbore is identified by.
Get the data
Free. You will be asked to confirm an email address before the files are built — that is the only gate, and it is there so we can tell you when a large export is ready.
What this is
Record type 11. The oil-schedule identity of a wellbore: oil/gas code, district, lease number and well number on the lease.
What you can do with it
Resolve which lease and well-on-lease an API number corresponds to, which is what production data is reported against.
Gotchas
A lease number is only unique with the oil/gas code and the district in it. Oil lease 027587 in District 08 and gas lease 027587 in District 08 are different leases; so is oil lease 027587 in District 09.
Record layout
8 columns. Byte positions are 1-based and come from the RRC record layout, so you can check our decoding against the original file yourself.
wb_well_ids
8 columns
| # | Column | Type | Bytes | RRC name | Meaning | Lookup |
|---|---|---|---|---|---|---|
| 1 |
api_county
key
join
|
text | — | — | The three-digit county component of the API number. For offshore wells this is the nearest onshore county, not the well's actual location. | — |
| 2 |
api_unique
key
join
|
text | — | — | The five-digit well component of the API number. Unique only in combination with the county code. | — |
| 3 |
row_no
key
|
smallint | — | — | Sequence number of this row within its parent record. Part of the key. | — |
| 4 |
oil_code
|
text | 3 | WB-OIL-CODE |
'O' when the identifier is an oil lease identifier. | Oil or gas schedule |
| 5 |
oil_district
|
text | 4-5 | WB-OIL-DISTRICT |
District of the oil lease. | — |
| 6 |
oil_lse_number
join
|
text | 6-10 | WB-OIL-LSE-NUMBER |
Oil lease number. | — |
| 7 |
oil_well_number
|
text | 11-16 | WB-OIL-WELL-NUMBER |
Well number on the oil lease. | — |
| 8 |
ingested_at
|
timestamptz | — | — | When the upstream pipeline last wrote this row. Not an RRC field — it is EZRRC's provenance stamp, and it is what the freshness badge is measured against. | — |
Code lookups used here
Every coded column in this dataset resolves to a real lookup table, so
a well code of G can be read as what it actually means.
Oil or gas schedule 2 values
Read by oil_code
Which schedule a lease is carried on. This is not decoration: an oil lease number and a gas lease number can be the same digits and mean different leases, so a lease key is only unique with this code and the district in it.
| Code | Means |
|---|---|
O |
Oil Carried on the oil proration schedule; lease numbers are oil lease numbers. |
G |
Gas Carried on the gas proration schedule; lease numbers are gas well IDs. |
Source: PDQ Dump user manual; values confirmed as the complete distinct set in texas.pdq_og_lease_cycle.oil_gas_code
What this joins to
The Railroad Commission never states these keys anywhere in the files. They are the reason the data is hard to use, so here they are with the exact columns on both sides.
Wellbore Well Identifiers joins to Full Wellbore Database (ASCII) on API county and API unique — many rows here share a single row there.
its oil-schedule lease and well numbers
How the wellbore is identified on the oil proration schedule. Keyed on the API county and unique number, which is how every record type in WBA091 hangs off its root record.
full-wellbore-ascii.api_county = wellbore-well-ids.api_county AND full-wellbore-ascii.api_unique = wellbore-well-ids.api_unique
Where this comes from
- Published by
- Texas Railroad Commission — the original page
- Original format
- Fixed-width Columns are byte ranges with no separators, described only in a scanned record layout.
- Update cadence
- Updated once a week (Weekly, with the wellbore database.)
- RRC download link
- GoAnywhere MFT
- Record layout manual
- Our table
texas.wb_well_ids
EZRRC is an independent mirror of public-domain data published by the Texas Railroad Commission. It is not affiliated with or endorsed by the RRC. For any legal or regulatory purpose, verify against the official RRC release.