WELL · 42-207-32743 · DISTRICT 7

Tamale #1

Y

Haskell County · Rule SW. (Conglomerate) field · Producing  · Vertical

Tamale #1 (API 42-207-32743) is a well in Haskell County operated by New Height Energy LLC, completed December 20, 2012 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued September 27, 2012, permitted to 7,000 ft.

It was permitted by Ppc Operating Company LLC and has since transferred to New Height Energy LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Burson Sand, Goen Lime, Conglomerate.

Its lease has reported 9.67K barrels of oil since December 2012, last reporting in July 2026.

Operator of record

New Height Energy LLC

Permitted by PPC Operating Company LLC; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Nov 4, 2025 · (432) 269-1562

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleNew Height Energy LLC
Production reportsNew Height Energy, LLCthrough Mar 2026
Latest permitPPC Operating Company LLCSep 27, 2012

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

7,000
total depth, ft
1
permits on file
Sep 27, 2012
last permit issued
Dec 20, 2012
completed
9.67K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2012 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Dec 20, 2012
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Tamale O-8-31150Rule, SW. (Conglomerate)New Height Energy, LLC19.67K0Dec 2012 – Jul 2026

Oil, barrels lease total

Last 12 months 338 · prior 12 390(-13%)

0204060202420252026

Chain of custody

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

  1. 1PPC Operating Company LLCJan 2013 → Dec 2017
  2. 2Relentless Permian Operating LLCJan 2018 → Dec 2022
  3. 3New Height Energy, LLCJan 2023 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
748518-99DrillPPC Operating Company LLCSep 19, 2012Sep 27, 2012Sep 28, 20127,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-31150————

Formation tops

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

FormationMD ftSubsea
Burson Sand5,014-3,380
Goen Lime5,267-3,633
Conglomerate5,855-4,221

Perforations

Perforated and open-hole intervals.

FromToType
5,8615,868Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62518112.25150 S
5.56,0907.875290 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 27, 2013Feb 25, 2013Yes

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