FIELDS AND POOLS · UNITED STATES
Abo fields and pools
A regulator names each reservoir it oversees: a field in Texas, a pool in New Mexico. The name carries the formation, which is how one formation can be followed across a state line.
State
Sort
Wells completed in the Abo → · The Abo formation →
12 ON FILE · PAGE 1 OF 1
| Field or pool | State | Formation | County | Active completions | Operators | Oil, 12 mo | Gas, 12 mo | Lifetime oil | Last reported |
|---|---|---|---|---|---|---|---|---|---|
| Justis; Abo, Mid (Gas) | New Mexico | Abo | Lea | 6 | 3 | 1,180 | 39,683 | 29,822 | Aug 2026 |
| Skaggs; Abo (Gas) | New Mexico | Abo | Lea | 4 | 2 | 389 | 72,140 | 174,558 | Aug 2026 |
| Pecos Slope; Abo (Gas) | New Mexico | Abo | Chaves | 769 | 16 | 0 | 3.6M | 53,519 | Aug 2026 |
| Pecos Slope; Abo, West (Gas) | New Mexico | Abo | Chaves | 191 | 3 | 0 | 133,002 | 12 | Aug 2026 |
| Sand Draw; Abo (G) | New Mexico | Abo | Chaves | 2 | 2 | 0 | 43,534 | 4,214 | Aug 2026 |
| Hightower; Abo (Gas) | New Mexico | Abo | Lea | 1 | 1 | 0 | 10,782 | 4,995 | Sep 2026 |
| Runyan Ranch; Abo (Gas) | New Mexico | Abo | Eddy | 4 | 2 | 0 | 6,072 | 314 | Aug 2026 |
| High Hope; Abo, East (Gas) | New Mexico | Abo | Eddy | 1 | 1 | 0 | 3,676 | 0 | Jul 2026 |
| Pine Lodge; Abo (Gas) | New Mexico | Abo | Chaves | 2 | 1 | 0 | 2,222 | 0 | Aug 2026 |
| Runyan Ranch; Abo, N. Gas | New Mexico | Abo | Eddy | 1 | 1 | 0 | 2,167 | 1 | Sep 2026 |
| Teague; Abo (Gas) | New Mexico | Abo | Lea | 2 | 1 | 0 | 583 | 19,241 | Aug 2026 |
| Oasis; Abo (Gas) | New Mexico | Abo | Chaves | 1 | 1 | 0 | 0 | 21,974 | Oct 2015 |
OIL IN BBL · GAS IN MCF · TWELVE MONTHS THROUGH THE STATE'S REPORTED-THROUGH MONTH
About this data
Each state regulator's field and pool registry, with the completions and the reported volumes of each. The formation is read from the name the regulator gave it and matched to one registry shared by every state; a name that gives no single formation has none. Nothing is estimated.
Developers: this page as JSON is GET /v1/data/fields, documented in the API reference.