Texas RRC Oil & Gas Well Operator Scraper
Texas RRC Oil & Gas Well Scraper — Operator & Lease Data
Scrape Texas Railroad Commission (RRC) oil and gas well records from the public EWA system. Returns API number, operator name, lease, field, county, district, well type, proration schedule status, and total drilled depth for wells across all 13 RRC districts. Covers 300,000+ wells.
What does the Texas RRC Oil & Gas Well Scraper do?
The actor queries the RRC Enhanced Web Access system by district, county (optional), and well type. It paginates across all result sets within RRC's 1,000-record-per-query limit and assembles a complete, structured dataset. No API key or account is required.
Current coverage is Texas RRC only. The actor slug references WVDEP but West Virginia DEP support has not been implemented — all records in this actor are Texas RRC data.
What data does it extract?
| Field | Description |
|---|---|
api_number |
8-digit API well number (RRC format) |
state |
State abbreviation (TX for all records) |
district |
RRC district code (01–10, 6E, 7B, 7C, 8A) |
county |
County name |
lease_number |
RRC oil lease number or gas well ID |
lease_name |
Name of the lease |
well_number |
Well number within the lease |
field_name |
Oil or gas field name |
operator_name |
Current operator company name |
well_type |
Well type code: PR (Producing), SH (Shut In), AB (Abandoned), TA (Temp Abandoned), IN (Injection), NP (No Production) |
on_schedule |
Whether well is on proration schedule (Y/N) |
api_depth |
Total drilled depth in feet |
source_url |
Direct URL to the well record on RRC EWA |
How to use it
{
"districts": ["08"],
"wellTypes": ["PR"],
"maxItems": 1000
}
Returns up to 1,000 producing wells in RRC District 08 (Permian Basin) across all counties. Scraping all producing wells in District 08 without a county filter returns approximately 85,000 records — plan run cost and time accordingly.
{
"districts": ["01", "02"],
"counties": ["015", "021"],
"wellTypes": ["PR", "SH"],
"maxItems": 500
}
Returns producing and shut-in wells in Austin and Bastrop counties within Districts 01 and 02.
| Parameter | Type | Required | Description |
|---|---|---|---|
districts |
array | Yes | RRC district codes: 01, 02, 03, 04, 05, 06, 6E, 7B, 7C, 08, 8A, 09, 10 |
counties |
array | No | Texas county FIPS codes (3-digit). Leave empty to iterate all producing counties in each district |
wellTypes |
array | Yes | Well type codes: PR, SH, AB, TA, IN, NP |
maxItems |
integer | Yes | Maximum number of well records to return |
County FIPS codes are the standard Texas 3-digit county identifiers (e.g. 015 for Austin County, 113 for Jeff Davis County, 227 for Midland County). The full list is published by the US Census Bureau and the Texas Association of Counties. Leave counties empty to let the actor iterate all oil-producing counties in each requested district.
Well type reference
| Code | Description |
|---|---|
| PR | Producing — currently producing oil or gas |
| SH | Shut In — capable but production suspended |
| AB | Abandoned — permanently plugged |
| TA | Temporarily Abandoned — inactive, not yet plugged |
| IN | Injection — used for enhanced recovery or disposal |
| NP | No Production — drilled but never produced |
Use cases
- Mineral rights research — identify operators and production status for specific leases, fields, or tracts across Texas counties
- Energy analytics and land data — enumerate wells by district, field, or operator for production analytics or basin mapping
- Landman and land brokerage databases — build or refresh lease and operator records across all 13 RRC districts
- Regulatory and ESG monitoring — track well status changes (e.g. producing to abandoned) across operator portfolios
Notes
- The RRC EWA returns a maximum of 1,000 records per district-county-well type query. The actor splits searches by county to stay within this limit and iterates all counties when none are specified.
- The actor inserts 300ms delays between requests to avoid overloading the RRC system.
api_depthis the total drilled depth from the API filing and may differ from producing perforations.
Results export as JSON, CSV, or Excel from the Apify dataset view.