OPERATORS · NEW MEXICO · OGRID 817
Anadarko Petroleum Corp
- Status with OCD
- Active
- Based in
- Midland, TX
- Registered as
- Well operator, Transporter
Anadarko Petroleum Corp has 70 wells on file in New Mexico and none of them active.
It last reported production in December 2002; nothing in the twelve months through August 2026.
- 0
- active wells of 65 drilled
- 0
- bbl oil, 12 months through Aug 2026
- 0
- Mcf gas, same 12 months
- 0
- APDs approved in 12 months · 0 not yet spudded
All 70 wells on file under this operator, searchable →
By county
The twelve months its wells of record reported, whoever operated them then.
By pool
Latest APDs
All of them →| Approved | Well | County | Proposed formation | Target depth | Now |
|---|---|---|---|---|---|
| Aug 9, 2001 | Paint 29 Federal #001 30-015-31955 | Eddy | Loco Hills Paddock | 5,000 | Cancelled |
| Nov 24, 1998 | Greer #005 30-025-34534 | Lea | Ellenburger | — | Cancelled |
| Oct 27, 1997 | Ballard C #004 30-015-29914 | Eddy | San Andres | 4,100 | Cancelled |
| Oct 8, 1997 | Travis a 6 Federal #001 30-015-29877 | Eddy | San Andres | 3,400 | Cancelled |
| May 16, 1996 | Welch Federal #001 30-015-22300 | Eddy | Bone Spring P&a 3-31-05 | 6,485 | Plugged (site released) |
| Nov 1, 1986 | Federal 11 #001 30-015-25086 | Eddy | — | — | Plugged (site released) |
| Dec 1, 1984 | Anderson #001 30-015-24163 | Eddy | — | — | Plugged (site released) |
| Dec 1, 1982 | Ballard Grayburg SA Unit #002 30-015-24266 | Eddy | — | — | Plugged (site released) |
| Jun 1, 1981 | Ballard Grayburg SA Unit #003 30-015-23713 | Eddy | — | — | Plugged (site released) |
| Apr 1, 1980 | Ballard Grayburg SA Unit #001Q 30-015-24244 | Eddy | — | — | Plugged (site released) |
About this data
New Mexico Oil Conservation Division (OCD). Anadarko Petroleum Corp is identified by its OGRID. Well counts are the wells it is operator of record for today; volumes are what it filed under that number, through Aug 2026 for production and Aug 2026 for injection. Nothing is estimated.
Developers: this page as JSON is GET /v1/data/operators/nm/817, documented in the API reference.