WELL · 42-081-31639 · DISTRICT 7

Davenport #1S

Y

Coke County · Fort Chadbourne W. (Deep) field · Shut IN  · Vertical

Davenport #1S (API 42-081-31639) is a well in Coke County operated by Goodrock Natural Resources LLC, completed February 3, 1995 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued July 5, 1994, permitted to 6,000 ft.

It was permitted by Rim Operating, Inc. and has since transferred to Goodrock Natural Resources LLC on the wellbore schedule.

Completion filings report one formation top, including Canyon.

No lease production has been reported under this well’s leases.

It holds an active disposal or injection permit.

Operator of record

Goodrock Natural Resources LLC

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

Tulsa, OK · P-5 Y, filed Aug 4, 2025 · 59 permits on file · (918) 633-1783

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleGoodrock Natural Resources LLC
Production reportsnone
Latest permitRim Operating, Inc.Jul 5, 1994

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

6,000
total depth, ft
1
permits on file
Jul 5, 1994
last permit issued
Feb 3, 1995
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 1995 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 3, 1995
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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
Davenport O-9-13737Fort Chadbourne, W. (Deep)Goodrock Natural Resources, LLC100Feb 1995 – Jul 2026

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
425402-99DrillRim Operating, Inc.Jun 29, 1994Jul 5, 1994Jan 8, 19956,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-13737————

Formation tops

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

FormationMD ftSubsea
CanyonCANYON REEF3,695-1,661

Perforations

Perforated and open-hole intervals.

FromToType
3,7654,446Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37538517.5385 S
8.6253,765111,250 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 24, 1995Feb 15, 1995Yes
00Feb 24, 1995——

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
6.2M
bbl, all reported
Feb 2026
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000082439W-14 DisposalActive3,0001003,750–4,750

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 0 · prior 12 0

0120252026

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