WELL · 42-363-34910 · DISTRICT 7

Hart Ranch 36 #1

Y

Palo Pinto County · Cumming (Conglomerate) field · Producing  · Vertical

Hart Ranch 36 #1 (API 42-363-34910) is a well in Palo Pinto County operated by Mogul Resources LLC, completed July 21, 2000 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued April 26, 2000, permitted to 4,999 ft.

It was permitted by Kokomo Energy, Inc. and has since transferred to Mogul Resources LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Caddo, Big Saline, Atoka, Marble Falls.

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

Operator of record

Mogul Resources LLC

Permitted by Kokomo Energy, Inc.; the EWA schedule now lists a different operator.

Cisco, TX · P-5 Y, filed Mar 4, 2026 · (254) 631-1404

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMogul Resources LLC
Production reportsMogul Resources, LLCthrough Oct 2024
Latest permitKokomo Energy, Inc.Apr 26, 2000

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

4,999
total depth, ft
1
permits on file
Apr 26, 2000
last permit issued
Jul 21, 2000
completed
0
cumulative oil, bbl
396K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2000 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 21, 2000
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

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
Hart Ranch 36 G-8-179297Cumming (Conglomerate)Mogul Resources, LLC10396KJul 2000 – Jul 2026

Gas, mcf lease total

Last 12 months 0 · prior 12 216(-100%)

050100202420252026

Chain of custody

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

  1. 1Kokomo Energy, Inc.Jul 2000 → Dec 2002
  2. 2Marjac Oil Company, Inc.Jan 2003 → Mar 2013
  3. 3Tracer Operating, Inc.Apr 2013 → Jun 2015
  4. 4Mogul Resources, LLCFeb 2018 → Oct 2024

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
494464-99DrillKokomo Energy, Inc.Apr 26, 2000Apr 26, 2000May 4, 20004,999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-179297————

Formation tops

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

FormationMD ftSubsea
Caddo3,260-1,903
Big Saline3,645-2,288
AtokaATOKA CONGLOMERATE3,790-2,433
Marble Falls4,096-2,739

Perforations

Perforated and open-hole intervals.

FromToType
3,9413,949Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62527312.25170 S
4.54,1817.875200 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
00Dec 16, 2000Aug 30, 2000Yes
00Nov 8, 2000——

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