WELL · 42-389-32529 · DISTRICT 8

Torrez State 61 #1H

Plugged

Reeves County · Toyah NW (Shale) field  · Horizontal

Torrez State 61 #1H (API 42-389-32529) is a plugged horizontal well in Reeves County, plugged February 20, 2020, last operated by Cog Operating LLC.

The RRC has issued one drilling permit, issued March 24, 2008, permitted to 18,000 ft.

It was permitted by Chesapeake Operating, Inc. and has since transferred to Cog Operating LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Lamar, Wolfcamp, Pennsylvanian.

Operator of record

COG Operating LLC

Permitted by Chesapeake Operating, Inc.; the EWA schedule now lists a different operator.

Based in
Midland, TX
P-5 status
Active – Extension (X)
P-5 last filed
Jun 2, 2026
Permits on file
4,568
Phone
(432) 683-7443

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCOG Operating LLC
Production reportsCOG Operating LLCthrough Jan 2018
Latest permitChesapeake Operating, Inc.Mar 24, 2008

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

18,000
total depth, ft
1
permits on file
Mar 24, 2008
last permit issued
Nov 26, 2008
completed
0
cumulative oil, bbl
1.53M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2008 THROUGH Feb 2020

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 26, 2008
Shut in
—
Plugged
Feb 20, 2020

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
Torrez State 61 G-10-247107Toyah, NW (Shale)COG Operating LLC101.53MNov 2008 – Feb 2020

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. 1Chesapeake Operating, Inc.Dec 2008 → Sep 2012
  2. 2Shell Western E&POct 2012 → Dec 2014
  3. 3COG Operating LLCJan 2015 → Jan 2018

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
657116-99DrillChesapeake Operating, Inc.Mar 11, 2008Mar 24, 2008Aug 9, 200818,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-10-247107————

Formation tops

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

FormationMD ftSubsea
Lamar3,294-243
WolfcampWFMP8,688-5,637
PennsylvanianPENN9,193-6,142

Perforations

Perforated and open-hole intervals.

FromToType
9,91610,087Perforated
10,24610,394Perforated
11,35413,690Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,55017.51,379 S
9.6259,31912.25810 S
5.513,9168.5480 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 5, 2009Jan 26, 2009Yes
00May 19, 2009——

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) and the University Lands library. 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/38932529, documented in the API reference.