OPERATORS · NEW MEXICO · OGRID 184357
Aghorn Operating Inc
- Status with OCD
- Active
- Based in
- Odessa, TX
- Registered as
- Well operator
Petrora groups this registration with Aghorn Operating, Inc., Texas (638 active wells). Aghorn Operating, Inc. across every state →
Aghorn Operating Inc has 5 wells on file in New Mexico and none of them active.
It last reported production in July 2018; nothing in the twelve months through August 2026.
Petrora groups it with one other registration; the company page adds them up.
- 0
- active wells of 5 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 5 wells on file under this operator, searchable →
Reported production by month
Volumes Aghorn Operating Inc filed under its OGRID on form C-115, through Aug 2026. They stay with the operator that filed them, so a well it bought shows here only from the month it took over.
Last 12 months 0 · prior 12 0
Aghorn Operating Inc: Oil by month.
By county
The twelve months its wells of record reported, whoever operated them then.
By pool
| Pool | Active wells | Oil, 12 mo | Gas, 12 mo |
|---|---|---|---|
| Square Lake; QU-GB-SA, North | 0 | 0 | 0 |
| Double L; Queen (Assoc) | 0 | 0 | 0 |
| Pollock; Wolfcamp, Northeast | 0 | 0 | 0 |
| Shugart; Yates-7RS-QU-Grayburg | 0 | 0 | 0 |
Latest APDs
All of them →| Approved | Well | County | Proposed formation | Target depth | Now |
|---|---|---|---|---|---|
| May 8, 1991 | McMillan #001 30-025-31226 | Lea | Wolfcamp | 11,900 | Spudded Dec 30, 1991 |
| Jul 1, 1981 | State #001 30-005-60903 | Chaves | Queen | 2,007 | Plugged (site released) |
About this data
New Mexico Oil Conservation Division (OCD). Aghorn Operating Inc 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/184357, documented in the API reference.