WELL · 42-021-31601 · DISTRICT 3

Kuhn - a - #2

Plugged

Bastrop County · Giddings (Austin Chalk-3) field  · Horizontal

Kuhn - A - #2 (API 42-021-31601) is a plugged horizontal well in Bastrop County, plugged October 11, 2012, last operated by Leexus Oil LLC.

The RRC has issued one drilling permit (amended once), issued May 16, 2008, permitted to 7,500 ft.

It was permitted by Diversity Petroleum, LP and has since transferred to Leexus Oil LLC on the wellbore schedule.

Completion filings report 5 formation tops, including Austin Chalk, Eagle Ford, False Buda, Buda.

Its lease has reported 2.78K barrels of oil and 500 mcf of gas since July 2008, last reporting in May 2014.

Operator of record

Leexus Oil LLC

Permitted by Diversity Petroleum, LP; the EWA schedule now lists a different operator.

Giddings, TX · P-5 Y, filed Apr 4, 2026 · 29 permits on file · (979) 540-8625

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLeexus Oil LLC
Production reportsDiversity Petroleum, LPthrough Aug 2009
Latest permitDiversity Petroleum, LPSep 12, 2008

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

7,500
total depth, ft
2
permits on file
Sep 12, 2008
last permit issued
Jul 8, 2008
completed
2.78K
cumulative oil, bbl
500
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2008 THROUGH May 2014

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 8, 2008
Shut in
—
Plugged
Oct 11, 2012

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
Kuhn - a - O-3-25557Giddings (Austin Chalk-3)Leexus Oil LLC12.78K500Jul 2008 – May 2014

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1Diversity Petroleum, LPJul 2008 → Aug 2009

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
660798-98DrillDiversity Petroleum, LPAug 25, 2008Sep 12, 2008Jun 5, 20087,500
660798-99DrillDiversity Petroleum, LPApr 30, 2008May 16, 2008Jun 4, 20087,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-25557————

Formation tops

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

FormationMD ftSubsea
Austin Chalk6,256-5,782
Eagle FordEAGLEFORD SHALE7,002-6,528
False Buda7,102-6,628
Buda7,127-6,653
Georgetown7,254-6,780

Perforations

Perforated and open-hole intervals.

FromToType
6,8226,848Perforated
6,8666,886Perforated
6,8926,912Perforated
6,9207,001Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,17012.251,065 S
77,3128.75466 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 10, 2010Sep 1, 2010Yes

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