WELLS · TEXAS · ONE ROW PER API NUMBER
Texas wells
Every well on the Railroad Commission's schedule or with a drilling permit on file, newest permit first: who operates it, where it is, the field it is completed in, its permits, and the last month its lease reported.What an API number is →
A full API number opens the well. Anything else filters the list below.
Production
Texas reports production by lease, so a well carries no volumes of its own: "Last reported" is the last month the lease it is tied to reported. How Texas production is reported →
6 WELLS · PAGE 1 OF 1
These wells on a map →| Well | Operator | County, field | Status | Depth, ft | Permit | Permits | Last reported |
|---|---|---|---|---|---|---|---|
| Marthann #c 342-327-30690 | Golden Oil and Ranch LLC only | MenardClear Creek (Cisco) | ActiveOil | 1,714 | Apr 21, 1989 | 1 | Nov 2024 |
| Marthann #c 142-327-30688 | Golden Oil and Ranch LLC only | MenardClear Creek (Cisco) | Shut inOil | 1,730 | Apr 14, 1989 | 1 | Nov 2024 |
| Marthann a #142-327-30638 | Sha-Jam Operating Corp. only | MenardClear Creek (Cisco) | PluggedOil | 1,750 | Oct 2, 1986 | 1 | — |
| Marthann #342-327-30619 | Golden Oil and Ranch LLC only | MenardClear Creek (Cisco) | ActiveOil | 1,730 | Jan 3, 1986 | 1 | Nov 2024 |
| Marthann #242-327-30620 | Golden Oil and Ranch LLC only | MenardClear Creek (Cisco) | ActiveOil | 1,730 | Jan 3, 1986 | 1 | Nov 2024 |
| Marthann #142-327-30582 | Golden Oil and Ranch LLC only | MenardClear Creek (Cisco) | ActiveOil | 3,600 | Oct 17, 1984 | 1 | Nov 2024 |
About this data
One row per API number: every well on the Railroad Commission wellbore schedule, and every API number a drilling permit names. Operator, field, status, and dates are the schedule's where it lists the well, the latest permit's otherwise. Permits on file counts every permit and amendment. Texas reports production by lease, so a well shows the last month its lease reported and no volumes. Nothing is estimated.
Developers: this page as JSON is GET /v1/data/wells?state=tx, documented in the API reference.