Legislative intelligence / 90R
SESSION 2027View project ↗

Civil Practice and Remedies Code § 64.091: RECEIVER FOR MINERAL INTERESTS OWNED BY NONRESIDENT OR ABSENTEE

No bill in the 90th Legislature changes this section yet

Follow this section in Texas Bill Atlas: a bill filed later that changes it shows up as new.

Part of Civil Practice and Remedies Code Chapter 64, with every bill that changes it.

Bills are matched to sections automatically from their text and can be missed, for example when a bill changes a whole chapter at once or renumbers sections. No bill listed here does not mean no bill changes this section.

Current law

Sec. 64.091. RECEIVER FOR MINERAL INTERESTS OWNED BY NONRESIDENT OR ABSENTEE. (a) The purpose of this section is to encourage the exploration and development of mineral resources.

(b) In the following actions, a district court or the business court may appoint a receiver for the mineral interest or leasehold interest under a mineral lease owned by a nonresident or absent defendant:

(1) an action that is brought by a person claiming or owning an undivided mineral interest in land in this state or an undivided leasehold interest under a mineral lease of land in this state and that has one or more defendants who have, claim, or own an undivided mineral interest in the same property; or

(2) an action that is brought by a person claiming or owning an undivided leasehold interest under a mineral lease of land in this state and that has one or more defendants who have, claim, or own an undivided leasehold interest under a mineral lease of the same property.

(b-1) The defendant for whom the receiver is sought must:

(1) be a person whose residence or identity is unknown or a nonresident; and

(2) have not paid taxes on the interest or rendered it for taxes during the five-year period immediately preceding the filing of the action.

(c) The plaintiff in the action must allege by verified petition and prove that he:

(1) has made a diligent but unsuccessful effort to locate the defendant; and

(2) will suffer substantial damage or injury unless the receiver is appointed.

(d) In an action under Subsection (b)(1):

(1) the plaintiff, in the verified petition, must name the last known owner or the last record owner of the interest as defendant;

(2) the plaintiff must serve notice on the defendant by publication as provided by the Texas Rules of Civil Procedure;

(3) the court may appoint as receiver the county judge and his successors or any other resident of the county in which the land is located;

(4) notwithstanding the Texas Rules of Civil Procedure, the applicant is not required to post bond; and

(5) the receiver is not required to post bond.

(e) A receivership created under this subchapter continues as long as the defendant or his heirs, assigns, or personal representatives fail to appear in court in person or by agent or attorney to claim the defendant's interest.

(f) As ordered by the court, the receiver shall immediately:

(1) execute and deliver to a lessee or successive lessees mineral leases on the outstanding undivided mineral interests;

(2) execute and deliver to a lessee or successive lessees an assignment of the outstanding undivided leasehold interest; and

(3) enter into a unitization agreement authorized by the Railroad Commission of Texas.

(g) A lease executed by a receiver under this section may authorize the lessee to pool and unitize land subject to the lease with adjacent land into a unit not to exceed 160 acres for an oil well or 640 acres for a gas well plus 10 percent tolerance or into a unit that substantially conforms

The section continues: whole chapter.

Links

Texas Bill Atlas is an independent research tool, not an official state website.

PLEASE READ

Before you use Texas Bill Atlas

An independent, open-source project. This site is not affiliated with, endorsed by, or operated by the Texas Legislature, the Texas Legislative Council, the Secretary of State, or any state agency.

Data may be incomplete, delayed, or wrong. Bill records are copied automatically from the legislature’s public files. Topic, agency, party, influence and last-action tags, and the full-text summaries written by Luna (an AI model), are automated interpretations and can be mistaken.

Not advice. Nothing here is legal, political, or professional advice. The project and its contributors make no warranty of accuracy or completeness and accept no liability for errors, omissions, or decisions made using this site.

Check the official record. Confirm anything that matters on Texas Legislature Online. Spotted a mistake? Report it on GitHub.

TEXAS BILL ATLAS

Privacy Policy

Last updated: November 11, 2026

Texas Bill Atlas is a free, independent, open-source project. We believe you should be able to research legislation without creating an account or providing personal information.

Information we collect

We do not require registration, names, email addresses, or other personal information to use the service.

We do not sell personal information, serve targeted advertising, or intentionally track individual browsing activity.

Analytics and security

We use Cloudflare for website delivery, security, and traffic analytics.

Cloudflare may process technical information such as IP addresses, browser details, request information, and website usage statistics. Cloudflare may also use cookies necessary for security and abuse prevention.

For more information, see Cloudflare's Privacy Policy.

Watchlists and saved preferences

Watchlists and preferences are stored locally in your browser by default.

If you choose to enable watchlist synchronization, we store the selected bill numbers, the member codes of legislators you follow, your saved searches (their names, search words and filters), filters, and hashed access keys on our server. View-only links show the bill numbers only.

No account or personal information is required. Anyone possessing a valid private access link may access the associated watchlist according to that link's permissions.

You can delete a synced watchlist using its edit access key. Inactive synced watchlists are automatically removed after approximately one year.

Technical data

Our servers may temporarily process IP addresses and request information for security, rate limiting, and reliable operation.

We do not use this information to build individual user profiles.

The site also loads certain external resources, including Google Fonts. Those providers may receive ordinary technical request information.

Third-party services

Links to government websites, GitHub, and other external services are governed by their respective privacy policies.

Changes

We may update this policy as the project develops. The current version will be available on this website with its updated date.

Questions

For questions about the project or its privacy practices, visit our GitHub repository.