WELLS · 30-015-26405 · NEW MEXICO · ARTESIA DISTRICT

Poker Lake Unit #073

ActiveVertical oil well

County
Eddy

A vertical oil well in Eddy County, New Mexico, operated by Maverick Operating, LLC. OCD status: active.

Spudded June 25, 1991.

Completed in one pool: Poker Lake; Delaware, South.

It has reported 73,103 bbl of oil, 58,875 Mcf of gas, and 222,406 bbl of water since December 1992; in the twelve months through August 2026, 225 bbl, 0 Mcf, and 263 bbl.

225
bbl oil, 12 months through Aug 2026
0
Mcf gas, same 12 months
263
bbl produced water, same 12 months
73,103
bbl oil since Dec 1992 · 58,875 Mcf gas

Reported production

Every month on file for this well on form C-115, summed across its pools and the operators that filed it. The newest months can still be amended.

Last 12 months 225 · prior 12 208(+8%)

010K20K30K1993199419951996199719981999200020012002200320042005200620072008200920102011201220132014201520162017201820192020202120222023202420252026

Poker Lake Unit #073: Oil by month.

Completions

ONE PER POOL THE WELL IS COMPLETED IN

PoolStatusPerforations, ftCompletedProducedOil, bblGas, McfWater, bbl
Poker Lake; Delaware, SouthActive · Pumping——Dec 1992 to Aug 202673,10358,875222,406

Operators of record

OperatorFromTo
Maverick Operating, LLCJan 20, 2012today
Guadalupe Operating LLPJan 1, 2003Jan 20, 2012
Summers Exploration CompanyJul 1, 2001Jan 1, 2003
Charles B Gillespie JrJul 1, 1990Jul 1, 2001

Well record

API number
30-015-26405
Location
A-33-24S-31E · 660 FNL, 660 FEL
Land
Federal
Property
Poker Lake Unit
APD
Approved Jul 1, 1990
Spudded
Jun 25, 1991

About this data

New Mexico Oil Conservation Division (OCD), from its public database extracts. Status and type are in OCD's own words. Production and injection are what operators filed on form C-115, by well and month; twelve-month figures end in Aug 2026, the last month whose filings are in. Locations are from the well's location plat and are approximate. Nothing is estimated.

Developers: this page as JSON is GET /v1/data/wells/3001526405, documented in the API reference.