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.

How it is laid out

The Railroad Commission publishes this as Fixed-width ASCII. Columns are byte ranges with no separators, described only in a scanned record layout. We decode it into a table you can open anywhere. It has 8 columns and about 667.1K rows.

The columns you will most likely want:

  • api_county The three-digit county component of the API number. For offshore wells this is the nearest onshore county, not …
  • api_unique The five-digit well component of the API number. Unique only in combination with the county code.
  • row_no Sequence number of this row within its parent record. Part of the key.
  • oil_code 'O' when the identifier is an oil lease identifier.
  • oil_district District of the oil lease.
  • oil_lse_number Oil lease number.

…and 2 more, all documented on the full page.

What we add

Resolve which lease and well-on-lease an API number corresponds to, which is what production data is reported against.

  • Decoded out of the Commission's original format into something Excel opens.
  • Filterable before you download, so you can take one county instead of the whole state.
  • The Commission's single-letter codes translated into words.

Worth knowing before you use it

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.

The full page lists every trap in this dataset.

Get it

People who want this usually want