WELLS · TEXAS · ONE ROW PER API NUMBER
Palo Cross LLC 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.
6 wells match
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 |
|---|---|---|---|---|---|---|---|
| Bird #142-367-34065 | Palo Cross LLC | ParkerNewark East (Barnett Shale) | PluggedGas | 8,500 | Oct 16, 2012 | 3 | May 2019 |
| Anthony #142-367-32068 | Palo Cross LLC | ParkerH. & R. (Bend Congl) | Temporarily abandonedGas | 4,724 | May 24, 1982 | 2 | Mar 2022 |
| Moore H. #142-363-32814 | Palo Cross LLC | Palo PintoMineral Wells S.(georgia Congl) | ActiveGas | 4,400 | Dec 9, 1981 | 1 | Apr 2026 |
| Dyment #1 C42-363-32637 | Palo Cross LLC | Palo PintoMineral Wells South (Strawn UP) | ActiveGas | 4,695 | Jun 5, 1981 | 2 | Apr 2026 |
| Collins #1A42-363-32567 | Palo Cross LLC | Palo PintoVan Dyke (Cisco 600) | ActiveGas | 803 | Feb 12, 1981 | 1 | Apr 2026 |
| Collins #142-363-32495 | Palo Cross LLC | Palo PintoMineral Wells S. (Atoka 4400) | ActiveGas | 4,581 | Nov 5, 1980 | 1 | Apr 2026 |
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.