WELL · 42-173-33554 · DISTRICT 8

Cox 32 #1

N

Glasscock County  · Vertical

Cox 32 #1 (API 42-173-33554) is a permitted well in Glasscock County filed by Laredo Petroleum, Inc.; no completion report is on file yet.

The RRC has issued 2 drilling permits (amended once) between 2009 and 2010, permitted to 10,000 ft.

Completion filings report 6 formation tops, including Yates, L Spraberry, Dean, Wolfcamp.

Its lease has reported 385K barrels of oil and 2.21M mcf of gas since February 2010, last reporting in July 2026. The lease carries 5 wells, so these are lease totals, not this well alone.

Operator of record

Laredo Petroleum, Inc.

Tulsa, OK · P-5 Y, filed Mar 8, 2024 · 1,795 permits on file · (918) 513-4570

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsCrescent Energy Operating, LLCthrough Apr 2026
Latest permitLaredo Petroleum, Inc.Nov 12, 2010
10,000
total depth, ft
3
permits on file
Nov 12, 2010
last permit issued
—
completed
385K
cumulative oil, bbl
2.21M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2010 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 lease this well is completed on; they carry 5 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Cox 32 O-10-40175Garden City, S. (Wolfcamp)Crescent Energy Operating, LLC5385K2.21MFeb 2010 – Jul 2026

Gas, mcf lease total

Last 12 months 81,473 · prior 12 68,856(+18%)

05K10K202420252026

Oil, barrels lease total

Last 12 months 7,579 · prior 12 7,304(+4%)

05001K202420252026

Chain of custody

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

  1. 1Laredo Petroleum, Inc.Feb 2010 → Jan 2023
  2. 2Vital Energy, Inc.Feb 2023 → Dec 2025
  3. 3Crescent Energy Operating, LLCJan 2026 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
704892-99RecompletionLaredo Petroleum, Inc.Nov 5, 2010Nov 12, 2010—10,000
686260-98DrillLaredo Petroleum, Inc.Aug 25, 2010Oct 22, 2009Jan 6, 200910,000
686260-99DrillLaredo Petroleum, Inc.Oct 19, 2009Oct 22, 2009—10,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-40175————

Formation tops

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

FormationMD ftSubsea
Yates1,665961
L Spraberry4,818-2,192
Dean6,756-4,130
Wolfcamp7,219-4,593
Canyon9,458-6,832
Strawn9,580-6,954

Perforations

Perforated and open-hole intervals.

FromToType
9,2329,376Perforated
9,4679,656Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37550017.5435 S
8.6252,87611910 S
5.59,7687.8751,410 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
00Oct 6, 2010Mar 8, 2010Yes
00Sep 24, 2010——

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