OPERATORS · NEW MEXICO · OGRID 233545

Bold Energy, L.P.

Status with OCD
Active
Based in
Midland, TX
Registered as
Well operator

The same name is registered in Texas (0 active wells). Bold Energy, L.P. across every state →

Bold Energy, L.P has 10 wells on file in New Mexico and none of them active.

It last reported production in October 2008; nothing in the twelve months through August 2026.

The same name and city are registered in Texas; the company page adds them up.

0
active wells of 3 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 10 wells on file under this operator, searchable →

By county

CountyActive wellsOil, 12 moGas, 12 mo
Lea0 of 200
Eddy0 of 100

The twelve months its wells of record reported, whoever operated them then.

By pool

Latest APDs

All of them →
ApprovedWellCountyProposed formationTarget depthNow
Mar 30, 2007Sandy Federal #003 30-015-35534EddyForty Niner Ridge Delaware SE8,050Cancelled
Mar 30, 2007Sandy Federal #005 30-015-35535EddyForty Niner Ridge Delaware SE8,000Cancelled
Mar 30, 2007Sandy Federal #006 30-015-35538EddyForty Niner Ridge Delaware8,000Cancelled
Jan 19, 2007Bell Lake #024 30-025-38291LeaDelaware8,600Cancelled
Apr 19, 2006Bathsheba State #001H 30-015-34793EddyWildcat Wolfcamp Gas8,267Cancelled
Mar 14, 2006Boaz State #001C 30-015-34689EddyMorrow11,800Cancelled
Feb 14, 2006Solomon State #001C 30-015-34613EddyTurkey Track Morrow Gas11,800Cancelled
Feb 1, 1983Antelope Ridge Unit #001 30-025-08486LeaPxa 10/13/200614,832Plugged (site released)
Nov 1, 1974Airport Grace #001 30-015-20829EddyP&a 01-24-208—Plugged (site released)

About this data

New Mexico Oil Conservation Division (OCD). Bold Energy, L.P. 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/233545, documented in the API reference.