WELL · 42-327-30939 · DISTRICT 7

Murr #1

Plugged

Menard County · Wilhelm Lane W. (Strawn Upper) field  · Vertical

Murr #1 (API 42-327-30939) is a plugged well in Menard County, plugged May 26, 2020, last operated by Cfo Resources Inc..

The RRC has issued one drilling permit, issued February 21, 2003, permitted to 3,900 ft.

It was permitted by Halvey Energy CO. and has since transferred to Cfo Resources Inc. on the wellbore schedule.

Completion filings report 4 formation tops, including King Sand, Palo Pinto, Fry Sand, Goen Lime.

Its lease has reported 12.8K barrels of oil and 10.1K mcf of gas since July 2003, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Cfo Resources Inc.

Permitted by Halvey Energy Co.; the EWA schedule now lists a different operator.

Corpus Christ, TX · P-5 Y, filed May 29, 2025 · (432) 853-4647

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCfo Resources Inc.
Production reportsCfo Resources, Inc.through Sep 2016
Latest permitHalvey Energy Co.Feb 21, 2003

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

3,900
total depth, ft
1
permits on file
Feb 21, 2003
last permit issued
Jun 16, 2003
completed
12.8K
cumulative oil, bbl
10.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2003 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 16, 2003
Shut in
—
Plugged
May 26, 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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Murr O-9-15426Wilhelm Lane, W. (Strawn, Upper)Cfo Resources, Inc.212.8K10.1KJul 2003 – Jul 2026

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. 1Halvey Energy Co.Jul 2003 → Oct 2004
  2. 2Spi Operations LLCNov 2004 → Aug 2006
  3. 3Cfo Resources, Inc.Jun 2007 → Sep 2016

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
528718-99DrillHalvey Energy Co.Feb 20, 2003Feb 21, 2003Mar 4, 20033,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-15426————

Formation tops

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

FormationMD ftSubsea
King Sand2,010194
Palo Pinto2,990-786
Fry Sand3,310-1,106
Goen Lime3,500-1,296

Perforations

Perforated and open-hole intervals.

FromToType
3,3363,348Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62534411255 S
4.53,4627.875475 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
00Aug 13, 2003Jul 7, 2003Yes
00Jul 23, 2003——

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