WELL · 42-359-30365 · DISTRICT 10

Bivins-Lit #1141

N

Oldham County  · Vertical

Bivins-Lit #1141 (API 42-359-30365) is a permitted well in Oldham County filed by Apache Corporation; no completion report is on file yet.

The RRC has issued 2 drilling permits between 2012 and 2014, permitted to 10,000 ft.

Completion filings report 2 formation tops, including Canyon, Strawn.

Its 2 leases have reported 3.66M barrels of oil and 6.35M mcf of gas since March 2011, last reporting in July 2026. The leases carry 63 wells, so these are lease totals, not this well alone.

Operator of record

Apache Corporation

Houston, TX · P-5 Y, filed Oct 4, 2025 · 9,754 permits on file · (713) 296-6400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsPresidio Petroleum LLCthrough Apr 2026
Latest permitApache CorporationFeb 11, 2014
10,000
total depth, ft
2
permits on file
Feb 11, 2014
last permit issued
—
completed
3.66M
cumulative oil, bbl
6.35M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2011 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
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 63 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bivins-Lit O-14-8366Paint Ridge (Canyon Granite WSH)Presidio Petroleum LLC342.94M5.15MMar 2011 – Jul 2026
Paint Ridge Unit O-14-9887Paint Ridge (Canyon Granite WSH)Presidio Petroleum LLC29723K1.2MJul 2019 – Jul 2026

Oil, barrels lease total

Last 12 months 79,979 · prior 12 90,907(-12%)

05K10K15K202420252026

Gas, mcf lease total

Last 12 months 134,637 · prior 12 158,130(-15%)

010K20K202420252026

Chain of custody

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

  1. 1Apache CorporationAug 2011 → Jun 2019
  2. 2Presidio Petroleum LLCJul 2019 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
778517-99RecompletionApache CorporationJan 30, 2014Feb 11, 2014—10,000
752926-99DrillApache CorporationDec 11, 2012Dec 14, 2012Dec 22, 201210,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-14-8366————
—— O-14-8366————
—— O-14-9887————

Formation tops

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

FormationMD ftSubsea
CanyonCANYON LIME9,017-5,703
CanyonCANYON GRANITE WASH9,237-5,923
Strawn9,476-6,162

Perforations

Perforated and open-hole intervals.

FromToType
9,2909,320Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
20557261,675 S
13.3754,07517.51,725 S
9.6257,51512.25670 S
5.59,7098.75380 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
00Mar 19, 2026Apr 17, 2013Yes
00Mar 18, 2026Apr 17, 2013Yes
00Oct 4, 2013Apr 17, 2013Yes

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