WELL · 42-235-35437 · DISTRICT 7

Sugg Farmar 19 #2

Y

Irion County · Spraberry (Trend Area) field · Producing  · Vertical

Sugg Farmar 19 #2 (API 42-235-35437) is a well in Irion County operated by Compass Energy Operating LLC, completed July 8, 2013 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued May 8, 2013, permitted to 8,000 ft.

It was permitted by Exco/Hgi JV Assets, LLC and has since transferred to Compass Energy Operating LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Clear Fork, Wolfcamp, Canyon.

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

Operator of record

Compass Energy Operating LLC

Permitted by Exco/Hgi JV Assets, LLC; the EWA schedule now lists a different operator.

Tulsa, OK · P-5 Y, filed Oct 4, 2025 · 27 permits on file · (325) 277-1754

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCompass Energy Operating LLC
Production reportsCompass Energy Operating, LLCthrough Apr 2026
Latest permitExco/Hgi JV Assets, LLCMay 8, 2013

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

8,000
total depth, ft
1
permits on file
May 8, 2013
last permit issued
Jul 8, 2013
completed
0
cumulative oil, bbl
479K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2013 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 8, 2013
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
Sugg Farmar '19' G-9-269764Sugg Ranch (Canyon)Compass Energy Operating, LLC10479KJul 2013 – Jul 2026

Gas, mcf lease total

Last 12 months 3,772 · prior 12 5,917(-36%)

05001K202420252026

Chain of custody

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

  1. 1Exco/Hgi JV Assets, LLCJul 2013 → Jun 2014
  2. 2Compass Energy Operating, LLCJul 2014 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
761788-99DrillExco/Hgi JV Assets, LLCMay 1, 2013May 8, 2013Jun 3, 20138,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-9-269764————

Formation tops

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

FormationMD ftSubsea
Clear ForkCLEARFORK2,506-105
Wolfcamp5,246-2,845
Canyon6,336-3,935

Perforations

Perforated and open-hole intervals.

FromToType
6,5056,630Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,02811450 S
4.56,8007.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
00Sep 16, 2013Aug 2, 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) and the University Lands library. 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/23535437, documented in the API reference.