WELL · 42-247-32399 · DISTRICT 4

Mestena Oil & Gas #26

Y

Jim Hogg County · Mestena Grande (Queen City Cons) field · Producing  · Vertical

Mestena Oil & Gas #26 (API 42-247-32399) is a well in Jim Hogg County operated by Bordertown Energy Resources LLC, completed August 3, 2007 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued May 3, 2007, permitted to 11,000 ft.

It was permitted by Cody Energy LLC and has since transferred to Bordertown Energy Resources LLC on the wellbore schedule.

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

Operator of record

Bordertown Energy Resources LLC

Permitted by Cody Energy LLC; the EWA schedule now lists a different operator.

Bryan, TX · P-5 Y, filed Aug 4, 2025 · 2 permits on file · (956) 614-0250

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBordertown Energy Resources LLC
Production reportsBordertown Energy Resources, LLCthrough Mar 2026
Latest permitCody Energy LLCMay 3, 2007

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

11,000
total depth, ft
2
permits on file
May 3, 2007
last permit issued
Aug 3, 2007
completed
0
cumulative oil, bbl
479K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2007 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 3, 2007
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Mestena Oil & Gas G-4-229062Mestena Grande (Queen City Cons)Bordertown Energy Resources, LLC10479KAug 2007 – Jul 2026

Gas, mcf lease total

Last 12 months 11,586 · prior 12 0

01K2K3K202420252026

Chain of custody

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

  1. 1Cody Energy LLCAug 2007 → Sep 2012
  2. 2Bluestone Natural Res. II, LLCOct 2012 → Dec 2019
  3. 3Blackbeard Operating, LLCJan 2020 → Nov 2020
  4. 4Hugoton Operating Company, Inc.Dec 2020 → Oct 2023
  5. 5Bordertown Energy Resources, LLCMay 2025 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
637793-98DrillCody Energy LLCJul 2, 2007May 3, 2007Jul 3, 200711,000
637793-99DrillCody Energy LLCApr 25, 2007May 3, 2007—11,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-229062————

Perforations

Perforated and open-hole intervals.

FromToType
9,8899,916Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,48512.25735 S
76,9008.75140 S
4.510,0206.125330 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
00Aug 27, 2007Aug 16, 2007Yes
00Aug 23, 2007——

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/24732399, documented in the API reference.