WELL · 42-233-33449 · DISTRICT 10

Dee O Gee #2

N

Hutchinson County · Panhandle Hutchinson County Fld. field  · Vertical

Dee O Gee #2 (API 42-233-33449) is a well in Hutchinson County operated by Lera, completed September 22, 2011.

The RRC has issued 2 drilling permits between 2011 and 2013, permitted to 3,500 ft.

Completion filings report 4 formation tops, including Brown Dolomite, Brown Dolomte, Moore County Lime, Granite Wash.

Its 2 leases have reported 1.06K barrels of oil and 107K mcf of gas since September 2011, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Lera

Borger, TX · P-5 Y, filed Jun 4, 2026 · 34 permits on file · (806) 886-0998

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLera
Production reportsBorger Resources 2 LLCthrough Apr 2026
Latest permitLeraJan 11, 2013

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

3,500
total depth, ft
2
permits on file
Jan 11, 2013
last permit issued
Sep 22, 2011
completed
1.06K
cumulative oil, bbl
107K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2011 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 22, 2011
Shut in
—
Plugged
—

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Dee O Gee G-14-276608Panhandle, WestBorger Resources 2 LLC10105KApr 2013 – Jul 2026
Dee O Gee O-14-8532Panhandle Hutchinson County Fld.Lera11.06K2.56KSep 2011 – Aug 2015

Gas, mcf lease total

Last 12 months 3,641 · prior 12 3,157(+15%)

0200400600202420252026

Chain of custody

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

  1. 1LeraOct 2011 → Jul 2016
  2. 2Ponderosa TX Operating LLCAug 2016 → Mar 2018
  3. 3Borger Resources 2 LLCMay 2018 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
752569-99RecompletionLeraDec 4, 2012Jan 11, 2013Apr 1, 20133,220
715239-99DrillLeraApr 28, 2011May 10, 2011Jul 1, 20113,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-14-276608————
—— O-14-8532————

Formation tops

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

FormationMD ftSubsea
Brown Dolomite2,330810
Brown Dolomte2,330810
Moore County Lime2,872268
Granite Wash3,002138

Perforations

Perforated and open-hole intervals.

FromToType
2,2432,753Perforated
2,9343,028Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62553112.25250 S
5.53,2107.875175 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
00May 11, 2015May 2, 2013Yes
00Oct 11, 2012Oct 27, 2011Yes

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