TEXAS · WELLS · STERLING COUNTY · PARRAMORE SELLERS LEASE · API 42-431-33014 · DISTRICT 7B
Parramore Sellers #1
Sterling County · Signal Peak (Wolfcamp) field · Vertical
Parramore Sellers #1 (API 42-431-33014) is a plugged well in Sterling County, plugged April 25, 2011, last operated by Sharp Image Energy Inc..
The RRC has issued one drilling permit (amended once), issued March 6, 2001, permitted to 8,110 ft.
Completion filings report one formation top, including Wolfcamp.
Operator of record
- Based in
- Big Spring, TX
- P-5 status
- Active (A)
- P-5 last filed
- Jul 16, 2026
- Permits on file
- 665
- Phone
- (432) 267-3126
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Sharp Image Energy Inc. |
| Production reports | none |
| Latest permit | Sharp Image Energy, Inc.Mar 6, 2001 |
- 8,110
- total depth, ft
- 2
- permits on file
- Mar 6, 2001
- last permit issued
- Dec 17, 2001
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Dec 2002 THROUGH Apr 2012
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Dec 17, 2001
- Shut in
- —
- Plugged
- Apr 25, 2011
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Parramore Sellers O-10-37076 | Signal Peak (Wolfcamp) | Sharp Image Energy, Inc. | 1 | 0 | 0 | Dec 2002 – Apr 2012 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 506147-98 | Drill | Sharp Image Energy, Inc. | Jun 1, 2001 | Mar 6, 2001 | — | 8,110 |
| 506147-99 | Drill | Sharp Image Energy, Inc. | Mar 6, 2001 | Mar 6, 2001 | May 5, 2001 | 8,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Dec 17, 2001 | Parramore Sellers O-10-37076 | Signal Peak (Wolfcamp) | Sharp Image Energy Inc. | Plugged | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,458 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| WolfcampUPPER WOLFCAMP | 6,711 | -4,253 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,711 | 6,775 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 2,200 | 11 | 950 S |
| 4.5 | 8,110 | 7.875 | 825 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jun 11, 2003 | May 1, 2003 | Yes |
| 00 | Jun 5, 2003 | — | — |
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.
- Wellbore filings for 42-431-33014 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-431-33014 → scanned completion filings
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/43133014, documented in the API reference.