WELL · 42-039-32611 · DISTRICT 3

Lemmer, J. L. #12

N

Brazoria County  · Vertical

Lemmer, J. L. #12 (API 42-039-32611) is a permitted well in Brazoria County filed by Denbury Onshore, LLC; no completion report is on file yet.

The RRC has issued 4 drilling permits between 1997 and 2023, permitted to 6,200 ft.

Completion filings report 2 formation tops, including U. Mio. D, Oakville.

Its 2 leases have reported 437K barrels of oil and 301K mcf of gas since January 1993, last reporting in July 2026. The leases carry 4 wells, so these are lease totals, not this well alone.

Operator of record

Denbury Onshore, LLC

Spring, TX · P-5 Y, filed Oct 4, 2025 · 789 permits on file · (713) 898-0085

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsDenbury Onshore, LLCthrough Nov 2025
Latest permitDenbury Onshore, LLCJul 19, 2023
6,200
total depth, ft
4
permits on file
Jul 19, 2023
last permit issued
—
completed
437K
cumulative oil, bbl
301K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

29.501684, -95.319163

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Brazoria County.

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 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Lemmer, J. L. O-3-7852Manvel, E. (Oakville #3)Denbury Onshore, LLC3437K301KJan 1993 – Jul 2026
Lemmer, J. L. O-3-28144Manvel (F.B. II, Oligocene)Denbury Onshore, LLC100Sep 2023 – Jul 2026

Oil, barrels lease total

Last 12 months 2 · prior 12 289(-99%)

0100200202420252026

Gas, mcf lease total

Last 12 months 104 · prior 12 1,485(-93%)

05001K1.5K202420252026

Chain of custody

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

  1. 1Texaco E & P Inc.Jan 1993 → Nov 1994
  2. 2North Central Oil Corp.Dec 1994 → Dec 2005
  3. 3Pogo Producing CompanyJan 2006 → Mar 2007
  4. 4Texcal Energy (GP) LLCApr 2007 → Apr 2010
  5. 5Energyquest II, LLCMay 2010 → Sep 2012
  6. 6Argent Energy (US) Holdings Inc.Oct 2012 → Apr 2015
  7. 7Denbury Onshore, LLCMay 2015 → Nov 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
884462-99RecompletionDenbury Onshore, LLCSep 29, 2022Jul 19, 2023Sep 17, 20236,200
885232-99RecompletionDenbury Onshore, LLCOct 26, 2022Oct 31, 2022—6,200
715777-99RecompletionEnergyquest II, LLCMay 5, 2011May 23, 2011—4,510
459325-99DrillNorth Central Oil Corp.Mar 3, 1997Mar 3, 1997Apr 12, 19976,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-7852————
—— O-3-28144————

Formation tops

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

FormationMD ftSubsea
U. Mio. D3,671-3,618
OakvilleOAKVILLE 13,933-3,880
OakvilleOAKVILLE 74,324-4,271

Perforations

Perforated and open-hole intervals.

FromToType
3,3903,406Perforated
4,0754,079Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,60012.25825 S
5.54,5047.875385 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
00Sep 3, 2024May 8, 2024—
00Apr 10, 2023Mar 8, 2023—
00Apr 1, 2023Mar 22, 2023—
00Jul 30, 1997Jun 12, 1997Yes
00Jul 14, 1997——

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

H. O. F. A. B42-039-33355

1.0 KM · Peles, LLC · Section with this well →

Fleming4,705-4,620
Anahuac4,930-4,845
Frio5,562-5,477
Miocene (undifferentiated)—
Het Lime - Disposal—
Caprock—
Otis - Disposal—
Oligocene - Disposal—

Belcher, W.T. 'B'42-039-32619

2.2 KM · Texcal Energy (GP) LLC · Section with this well →

U Mio A3,474-3,421
U. Mio A3,474-3,421
U. Mio. A3,474-3,421
Oakville3,915-3,862
Oakville3,915-3,862
Mio 45504,515-4,462
Frio5,530-5,477

West Hastings Unit42-039-00435

5.0 KM · Denbury Onshore, LLC · Section with this well →

A46,182-6,137
A56,272-6,227
A1—
A2—
A3—

West Hastings Unit42-039-33192

5.0 KM · Denbury Onshore, LLC · Section with this well →

Miocene (undifferentiated)2,686-2,644
Miocene (undifferentiated)2,686-2,644
Caprock5,285-5,243
Frio6,164-6,122
Frio6,164-6,122
Het Lime - Disposal—
Otis - Disposal—
Oligocene - Disposal—

West Hastings Unit42-039-33099

5.0 KM · Denbury Onshore, LLC · Section with this well →

M103,867-3,826
M 103,867-3,826
M114,350-4,309
M 114,350-4,309
M 124,532-4,491
M124,532-4,491

West Hastings Unit42-039-33088

5.0 KM · Denbury Onshore, LLC · Section with this well →

Anahuac5,235-5,193
B16,566-6,524
B26,587-6,545

West Hastings Unit42-039-33086

5.0 KM · Denbury Onshore, LLC · Section with this well →

M114,282-4,240
M134,605-4,563
M14A4,867-4,825

West Hastings Unit42-039-33079

5.5 KM · Denbury Onshore, LLC · Section with this well →

M134,614-4,572
M114,721-4,679
M144,751-4,709

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