FIELDS AND POOLS · UNITED STATES
Cisco 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.
34 fields and pools match
Sort
Wells completed in the Cisco → · The Cisco formation →
34 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 |
|---|---|---|---|---|---|---|---|---|---|
| Vacuum; Cisco-Canyon, Northeast | New Mexico | Cisco-Canyon | Lea | 2 | 1 | 245,872 | 309,632 | 312,582 | Sep 2026 |
| Maljamar; Cisco | New Mexico | Cisco | Lea | 3 | 2 | 17,276 | 68,999 | 648,255 | Sep 2026 |
| Fren; Cisco-Canyon (O) | New Mexico | Cisco-Canyon | Eddy | 2 | 2 | 9,722 | 31,387 | 115,967 | Sep 2026 |
| Kemnitz; Cisco, West | New Mexico | Cisco | Lea | 1 | 1 | 6,078 | 20,641 | 134,499 | Sep 2026 |
| Kemnitz; Cisco, South | New Mexico | Cisco | Lea | 1 | 1 | 4,776 | 1,203 | 163,267 | Sep 2026 |
| Mescalero; Cisco, Northeast | New Mexico | Cisco | Lea | 1 | 1 | 2,861 | 6,959 | 79,959 | Aug 2026 |
| Wildcat; Cisco | New Mexico | Cisco | Eddy +1 | 1 | 1 | 2,555 | 27,785 | 81,305 | Sep 2026 |
| WC-015 G-01 S162728P; Cisco | New Mexico | Cisco | Eddy | 1 | 1 | 5 | 0 | 2,186 | Sep 2026 |
| Loco Hills; Cisco | New Mexico | Cisco | Eddy | 1 | 1 | 0 | 231 | 4,411 | Aug 2026 |
| Anderson Ranch; Cisco-Canyon | New Mexico | Cisco-Canyon | Lea | 0 | 0 | 0 | 0 | 18,369 | Feb 2002 |
| Anderson Ranch; Cisco-Canyon, North | New Mexico | Cisco-Canyon | Lea | 0 | 0 | 0 | 0 | 1.2M | Jan 2021 |
| Baish; Cisco | New Mexico | Cisco | Lea | 0 | 0 | 0 | 0 | 29,861 | Aug 2015 |
| Bear Grass Draw; Cisco | New Mexico | Cisco | Eddy | 0 | 0 | 0 | 0 | 2,338 | — |
| Cedar Lake; Cisco | New Mexico | Cisco | Eddy | 0 | 0 | 0 | 0 | 1,529 | Jun 1999 |
| Hume; Cisco | New Mexico | Cisco | — | 0 | 0 | 0 | 0 | 0 | — |
| Jenkins; Cisco | New Mexico | Cisco | Lea | 0 | 0 | 0 | 0 | 0 | — |
| Kemnitz; Cisco | New Mexico | Cisco | Lea | 0 | 0 | 0 | 0 | 70,930 | May 2020 |
| Leamex; Cisco, West | New Mexico | Cisco | Lea | 0 | 0 | 0 | 0 | 6,056 | Feb 2008 |
| Maljamar; Cisco-Canyon, West | New Mexico | Cisco-Canyon | Lea | 0 | 0 | 0 | 0 | 9,571 | Nov 2002 |
| Prairie; Cisco, South | New Mexico | Cisco | Roosevelt | 0 | 0 | 0 | 0 | 0 | — |
| Ranger Lake; Cisco, East | New Mexico | Cisco | Lea | 0 | 0 | 0 | 0 | 15 | Dec 2008 |
| Vacuum; Cisco | New Mexico | Cisco | Lea | 0 | 0 | 0 | 0 | 89,586 | Aug 2009 |
| WC-015 G-07 S193013A; Cisco-Canyon | New Mexico | Cisco-Canyon | — | 0 | 0 | 0 | 0 | 0 | — |
| WC-025 G-08 S173430M; Cisco-Canyon | New Mexico | Cisco-Canyon | Lea | 0 | 0 | 0 | 0 | 0 | — |
| WC-025 G-08 S183412L; Cisco | New Mexico | Cisco | Lea | 0 | 0 | 0 | 0 | 0 | — |
| WC-025 G-08 S203222N; Cisco-Canyon | New Mexico | Cisco-Canyon | — | 0 | 0 | 0 | 0 | 0 | — |
| WC-025 G-10 S213234N; Cisco-Canyon | New Mexico | Cisco-Canyon | Lea | 0 | 0 | 0 | 0 | 0 | — |
| WC-035 G-01 S141107P; Cisco | New Mexico | Cisco | Otero | 0 | 0 | 0 | 0 | 0 | — |
| WC Fren; Cisco-Canyon, West | New Mexico | Cisco-Canyon | — | 0 | 0 | 0 | 0 | 0 | — |
| Wildcat G-05 S103217L; Cisco-Canyon | New Mexico | Cisco-Canyon | Lea | 0 | 0 | 0 | 0 | 3,088 | Dec 2012 |
| Wildcat G06 S011928J; Cisco (O) | New Mexico | Cisco | — | 0 | 0 | 0 | 0 | 0 | — |
| Wildcat G07 S183231J; Cisco-Canyon | New Mexico | Cisco-Canyon | Lea | 0 | 0 | 0 | 0 | 0 | — |
| Wildcat G-08 S163402G; Cisco-Canyon | New Mexico | Cisco-Canyon | Lea | 0 | 0 | 0 | 0 | 93 | Dec 2013 |
| Wildcat Hills; Cisco | New Mexico | Cisco | Eddy | 0 | 0 | 0 | 0 | 0 | — |
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.