TEXAS · WELLS · HOOD COUNTY · RANDLE LEASE · API 42-221-31344 · DISTRICT 7C

Randle #4H

On schedule

Hood County · Newark East (Barnett Shale) field · Producing  · Horizontal

Randle #4H (API 42-221-31344) is a horizontal well in Hood County operated by Eagleridge Operating LLC, completed September 19, 2007 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued April 3, 2007, permitted to 6,132 ft.

It was permitted by Burlington Resources O & G CO LP and has since transferred to Eagleridge Operating LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Big Saline, Marble Falls, Barnett.

Its lease has reported 2.47K barrels of oil and 1.75M mcf of gas since September 2007, last reporting volume in August 2026.

Operator of record

Eagleridge Operating LLC

Permitted by Burlington Resources O & G Co LP; the EWA schedule now lists a different operator.

Based in
Dallas, TX
P-5 status
Active – Extension (X)
P-5 last filed
Apr 8, 2026
Permits on file
129
Phone
(214) 295-6704

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEagleridge Operating LLC
Production reportsEagleridge Operating, LLCthrough Apr 2026
Latest permitBurlington Resources O & G Co LPApr 3, 2007

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

6,132
total depth, ft
2
permits on file
Apr 3, 2007
last permit issued
Sep 19, 2007
completed
2.47K
cumulative oil, bbl
1.75M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · SEP 2007 THROUGH AUG 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Sep 19, 2007
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH AUG 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
Randle G-13-234514Newark, East (Barnett Shale)Eagleridge Operating, LLC12.47K1.75MSep 2007 – Aug 2026

Gas, mcf lease total

Last 12 months 35,516 · prior 12 40,638(-13%)

02K4K6K202420252026

Wells named Randle

Eagleridge Operating LLC's other wells filed under this lease name in Hood County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Burlington Resources O & G Co LPSep 2007 → Dec 2010
  2. 2Premier Natural Resources Ii,llcJan 2011 → Feb 2015
  3. 3Trinity River Energy Oper, LLCMar 2015 → Jun 2017
  4. 4Eagleridge Operating, LLCJul 2017 → Aug 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
636078-98DrillBurlington Resources O & G Co LPJul 23, 2008Apr 3, 2007Jun 9, 20079,000
636078-99DrillBurlington Resources O & G Co LPMar 28, 2007Apr 3, 2007Jun 9, 20079,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Sep 19, 2007Randle G-13-234514Newark East (Barnett Shale)Eagleridge Operating LLCProducing6,132

Formation tops

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

FormationMD ftSubsea
Big SalineBIG SALINE J4,270-3,336
Marble Falls4,534-3,600
Barnett5,023-4,089

Perforations

Perforated and open-hole intervals.

FromToType
6,5009,081Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62582012.25390 S
5.59,1507.875640 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00May 1, 2008Nov 1, 2007Yes
00Apr 24, 2008——

Well logs

1 log loaded from the RRC's log index, the latest received Jun 29, 2010. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
RESISTIVITYSpans Big Saline, Marble Falls, BarnettTIFF50 to 6,282Jun 29, 2010run Jun 18, 20073.70

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

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