TEXAS · WELLS · WHEELER COUNTY · HUNTER-HEFLEY 34 LEASE · API 42-483-33469 · DISTRICT 08

Hunter-Hefley 34 #7H

Y

Wheeler County · Buffalo Wallow (Granite Wash) field · Producing  · Horizontal

Hunter-Hefley 34 #7H (API 42-483-33469) is a horizontal well in Wheeler County operated by Unbridled Resources LLC, completed April 10, 2013 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended twice), issued May 1, 2012, permitted to 11,890 ft.

It was permitted by Enervest Operating, L.L.C. and has since transferred to Unbridled Resources LLC on the wellbore schedule.

Completion filings report 12 formation tops, including T/Tonkawa, Kansas City, Cleveland, Marmaton.

Its lease has reported 93.6K barrels of oil and 6.94M mcf of gas since April 2013, last reporting volume in April 2026.

Operator of record

Unbridled Resources LLC

Permitted by Enervest Operating, L.L.C.; the EWA schedule now lists a different operator.

Based in
Oklahoma City, OK
P-5 status
Active (A)
P-5 last filed
Dec 17, 2025
Permits on file
6
Phone
(318) 751-3917

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleUnbridled Resources LLC
Production reportsUnbridled Resources, LLCthrough Apr 2026
Latest permitEnervest Operating, L.L.C.May 1, 2012

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

11,890
total depth, ft
3
permits on file
May 1, 2012
last permit issued
Apr 10, 2013
completed
93.6K
cumulative oil, bbl
6.94M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2013 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 10, 2013
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Hunter-Hefley 34 G-14-276283Buffalo Wallow (Granite Wash)Unbridled Resources, LLC193.6K6.94MApr 2013 – Apr 2026

Gas, mcf lease total

Last 12 months 427,868 · prior 12 308,488(+39%)

050K100K202420252026

Chain of custody

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

  1. 1Linn Operating, Inc.Apr 2013 → Dec 2014
  2. 2Enervest Operating, L.L.C.Jan 2015 → Mar 2018
  3. 34P Energy Texas, LLCApr 2018 → Oct 2020
  4. 4Unbridled Resources, LLCNov 2020 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
738262-95DrillEnervest Operating, L.L.C.Mar 15, 2017May 1, 2012May 29, 201212,430
738262-98DrillLinn Operating, Inc.May 10, 2012May 1, 2012May 29, 201212,430
738262-99DrillLinn Operating, Inc.Apr 16, 2012May 1, 2012May 28, 201212,430

Completions

CompletedLeaseFieldOperatorStatusDepth
Apr 10, 2013Hunter-Hefley 34 G-14-276283Buffalo Wallow (Granite Wash)Unbridled Resources LLCProducing11,890

Formation tops

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

FormationMD ftSubsea
T/Tonkawa9,105-6,471
Kansas CityKANSAS CITY 'A'10,031-7,397
Cleveland10,489-7,855
Marmaton10,689-8,055
Cherokee Marker11,108-8,474
Carr GW11,350-8,716
Caldwell GW11,398-8,764
Britt GW11,480-8,846
GW 'A'11,605-8,971
GW "B"11,839-9,205
Britt GW——
Cherokee——
Tonkawa——

Perforations

Perforated and open-hole intervals.

FromToType
12,29116,306Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37562017.5790 S
9.6256,77212.25740 S
712,2418.75365 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 9, 2017Apr 20, 2017—
00Apr 8, 2015May 16, 2013Yes

Well logs

2 logs loaded from the RRC's log index, the latest received May 24, 2016. 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 Kansas City, Cleveland, Marmaton, Cherokee Marker, Carr Gw, Caldwell Gw, Britt Gw, Gw 'A', Gw "B"TIFF10,100 to 16,350May 24, 2016run Mar 5, 20130.47
RESISTIVITYSpans Cherokee Marker, Carr Gw, Caldwell Gw, Britt Gw, Gw 'A', Gw "B"TIFF11,252 to 12,018Apr 4, 2016run Jan 27, 20130.93

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