WELL · 42-321-32186 · DISTRICT 3

Livers Unit #01

Plugged

Matagorda County · Collegeport (8A) field  · Vertical

Livers Unit #01 (API 42-321-32186) is a plugged well in Matagorda County, plugged October 2, 2014, last operated by Sanchez Oil & Gas Corporation.

The RRC has issued one drilling permit, issued October 2, 2007, permitted to 5,950 ft.

It was permitted by Zachry Exploration, Ltd. and has since transferred to Sanchez Oil & Gas Corporation on the wellbore schedule.

Completion filings report 7 formation tops, including 1a Sand, 4 Sand, 5 Sand, 7c Sand.

Operator of record

Sanchez Oil & Gas Corporation

Permitted by Zachry Exploration, Ltd.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Feb 4, 2026 · 541 permits on file · (956) 722-8092

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSanchez Oil & Gas Corporation
Production reportsSanchez Oil & Gas Corporationthrough Sep 2012
Latest permitZachry Exploration, Ltd.Oct 2, 2007

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

5,950
total depth, ft
1
permits on file
Oct 2, 2007
last permit issued
Jun 5, 2011
completed
0
cumulative oil, bbl
170K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2008 THROUGH Mar 2015

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 5, 2011
Shut in
—
Plugged
Oct 2, 2014

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
Livers Unit G-3-235540Collegeport (8A)Sanchez Oil & Gas Corporation10170KApr 2008 – Mar 2015

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. 1Zachry Exploration, Ltd.Apr 2008 → Jan 2009
  2. 2Zachry Exploration, Inc.Feb 2009 → Feb 2009
  3. 3Sanchez Oil & Gas CorporationMar 2009 → Sep 2012

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
644233-99DrillZachry Exploration, Ltd.Aug 10, 2007Oct 2, 2007Nov 27, 20075,950

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-235540————

Formation tops

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

FormationMD ftSubsea
1A Sand3,650-3,637
4 Sand3,945-3,932
5 Sand4,150-4,137
7C Sand5,300-5,287
8 Sand5,580-5,567
9B Sand5,820-5,807
9D Sand5,820-5,807

Perforations

Perforated and open-hole intervals.

FromToType
5,3075,313Perforated
5,5785,580Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62591512.25334 S
2.8755,9557.875685 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
00Jun 18, 2012Jul 7, 2011—
00Jun 17, 2008May 5, 2008Yes
00Jun 2, 2008——

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