WELL · 42-235-33815 · DISTRICT 7

Farmar - Sugg #2228

Y

Irion County · Rock Pen (Clearfork) field · Producing  · Vertical

Farmar - Sugg #2228 (API 42-235-33815) is a well in Irion County operated by Core Petro LLC, completed July 3, 2001 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued May 25, 2001, permitted to 3,900 ft.

It was permitted by Armor Petroleum, Inc. and has since transferred to Core Petro LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Base Cretaceous (marker), San Angelo, Clear Fork.

Its lease has reported 69.8K barrels of oil and 6.09K mcf of gas since July 2001, last reporting in July 2026.

Operator of record

Core Petro LLC

Permitted by Armor Petroleum, Inc.; the EWA schedule now lists a different operator.

Abilene, TX · P-5 Y, filed Aug 4, 2025 · (325) 338-8717

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCore Petro LLC
Production reportsCore Petro, LLCthrough Apr 2026
Latest permitArmor Petroleum, Inc.May 25, 2001

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
May 25, 2001
last permit issued
Jul 3, 2001
completed
69.8K
cumulative oil, bbl
6.09K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2001 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 3, 2001
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
Farmar - Sugg O-9-15155Rock Pen (Clearfork)Core Petro, LLC169.8K6.09KJul 2001 – Jul 2026

Oil, barrels lease total

Last 12 months 496 · prior 12 774(-36%)

050100202420252026

Chain of custody

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

  1. 1Armor Petroleum, Inc.Jul 2001 → Apr 2021
  2. 2Core Petro, LLCJun 2021 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
509175-99DrillArmor Petroleum, Inc.May 18, 2001May 25, 2001May 30, 20013,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-15155————

Formation tops

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

FormationMD ftSubsea
Base Cretaceous (marker)BASE OF CRETACEOUS3302,061
San Angelo1,670721
Clear ForkCLEARFORK3,604-1,213

Perforations

Perforated and open-hole intervals.

FromToType
3,6043,611Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62535311160 S
5.53,6807.875480 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 6, 2001Jul 13, 2001Yes
00Jul 19, 2001——

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