WELL · 42-479-40237 · DISTRICT 4

Hubberd William B2 #82

Y

Webb County · Hubberd (Lobo) field · Producing  · Vertical

Hubberd William B2 #82 (API 42-479-40237) is a well in Webb County operated by Columbus Energy LLC, completed July 31, 2008 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued June 5, 2008, permitted to 9,500 ft.

It was permitted by Forest Oil Corporation and has since transferred to Columbus Energy LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Lobo 1, Lobo 3, Lobo 6.

No lease production has been reported under this well’s leases.

Operator of record

Columbus Energy LLC

Permitted by Forest Oil Corporation; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Apr 4, 2026 · 51 permits on file · (956) 722-5238

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleColumbus Energy LLC
Production reportsColumbus Energy, LLCthrough Apr 2026
Latest permitForest Oil CorporationJun 5, 2008

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

9,500
total depth, ft
1
permits on file
Jun 5, 2008
last permit issued
Jul 31, 2008
completed
0
cumulative oil, bbl
161K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2008 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 31, 2008
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Hubberd, William "B2" G-4-241991Hubberd (Lobo)Columbus Energy, LLC10161KJul 2008 – Jul 2026

Gas, mcf lease total

Last 12 months 3,545 · prior 12 1,205(+194%)

0200400600202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Forest Oil CorporationJul 2008 → Jun 2010
  2. 2Columbus Energy, LLCJul 2010 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
662148-99DrillForest Oil CorporationMay 15, 2008Jun 5, 2008Jun 20, 20089,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-241991————

Formation tops

As filed on W-2/G-1. Subsea from 468 ft elevation.Download CSV →

FormationMD ftSubsea
Lobo 18,300-7,832
Lobo 38,525-8,057
Lobo 68,854-8,386

Perforations

Perforated and open-hole intervals.

FromToType
8,3068,313Perforated
8,3328,346Perforated
8,3548,366Perforated
8,3988,404Perforated
8,8858,910Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62585012.25206 S
76,4038.75420 S
3.59,0006.25330 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Nov 20, 2008Sep 16, 2008Yes
00Nov 12, 2008——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

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