WELL · 42-485-46298 · DISTRICT 9
Parrish #4
Wichita County · Wichita County (Special) field · Shut IN · Vertical
Parrish #4 (API 42-485-46298) is a well in Wichita County operated by S&G Oil LLC, completed October 18, 2021 and listed as shut in on the RRC schedule.
The RRC has issued one drilling permit, issued August 27, 2021, permitted to 2,000 ft.
Completion filings report 9 formation tops, including Tannehill, Cisco, Thomas Sand, Gunsight.
Its lease has reported 10.6K barrels of oil since January 2021, last reporting in July 2026. The lease carries 4 wells, so these are lease totals, not this well alone.
Operator of record
Wichita Falls, TX · P-5 Y, filed Jun 4, 2026 · 49 permits on file · (940) 224-7463
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | S&G Oil LLC |
| Production reports | S&G Oil LLCthrough Mar 2026 |
| Latest permit | S&G Oil LLCAug 27, 2021 |
- 2,000
- total depth, ft
- 1
- permits on file
- Aug 27, 2021
- last permit issued
- Oct 18, 2021
- completed
- 10.6K
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 2021 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Oct 18, 2021
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active
Surface location
34.054194, -98.843808
OpenStreetMap → · Google Maps →
Permit surface location from the RRC GIS record, in Wichita County.
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; they carry 4 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Parrish O-13-34001 | Wichita County (Special) | S&G Oil LLC | 4 | 10.6K | 0 | Jan 2021 – Jul 2026 |
Oil, barrels lease total
Last 12 months 318 · prior 12 724(-56%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1S&G Oil LLCJan 2021 → Mar 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 872019-99 | Drill | S&G Oil LLC | Aug 16, 2021 | Aug 27, 2021 | Oct 12, 2021 | 2,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-13-34001 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Download CSV →
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 4.5 | 1,988 | 6.75 | 310 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 | May 13, 2022 | Apr 28, 2022 | Yes |
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-485-46298 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-485-46298 → 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.
Nearby wells and their tops
NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM
Draw a cross-section
This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.
Parrish42-485-46251
0.1 KM · S&G Oil LLC · Section with this well →
| Tannehill | 420 | |
| Cisco | 1,200 | |
| Thomas Sand | 1,550 | |
| Gunsight | 1,880 | |
| Gunsight | 1,890 | |
| Bluff Creek Sand | — | |
| Vogstberger | — | |
| Strawn | — |
10 TOPS · FIRST 8
Parrish42-485-46299
0.1 KM · S&G Oil LLC · Section with this well →
| Tannehill | 450 | |
| Cisco | 1,130 | |
| Thomas Sand | 1,530 | |
| Gunsight | 1,874 | |
| Gunsight | 1,900 | |
| Bluff Creek Sand | — | |
| Canyon | — | |
| KMA | — |
10 TOPS · FIRST 8
Parrish42-485-46278
0.1 KM · S&G Oil LLC · Section with this well →
| Tannehill | 440 | |
| Cisco | 820 | |
| Thomas Sand | 1,540 | |
| Gunsight | 1,886 | |
| Gunsight | 1,910 | |
| Canyon | — | |
| Strawn | — | |
| KMA | — |
10 TOPS · FIRST 8
Hill -A-42-485-46279
0.1 KM · S&G Oil LLC · Section with this well →
| Tannehill | 435 | |
| Cisco | 1,130 | |
| Thomas Sand | 1,446 | |
| Gunsight | 1,884 | |
| Gunsight | 1,918 | |
| Strawn | — | |
| KMA | — | |
| Canyon | — |
10 TOPS · FIRST 8
Parrish42-485-46314
0.2 KM · S&G Oil LLC · Section with this well →
| Cisco | 672 | |
| Thomas Sand | 1,546 | |
| Vogstberger | — | |
| Bluff Creek Sand | — | |
| Caddo | — | |
| Canyon | — | |
| Gunsight | — | |
| Gunsight | — |
10 TOPS · FIRST 8
Hill42-485-46240
0.3 KM · S&G Oil LLC · Section with this well →
| Tannehill | 450 | |
| Cisco | 950 | |
| Thomas Sand | 1,660 | |
| Gunsight | 1,920 | |
| Gunsight | 1,930 | |
| Canyon | — | |
| Vogstberger | — | |
| Strawn | — |
11 TOPS · FIRST 8
Gillis, Bruce42-485-46365
2.1 KM · Bonfire Operating LLC · Section with this well →
| Tannehill | 950 | 188 |
| Cisco | 1,200 | -62 |
| Thomas Sand | 1,370 | -232 |
| Gunsight | 1,550 | -412 |
| Gunsight | 1,560 | -422 |
| Canyon | 1,570 | -432 |
| Bluff Creek Sand | 1,600 | -462 |
| Strawn | 1,890 | -752 |
10 TOPS · FIRST 8
Marriott, J.H.42-485-46104
2.6 KM · S&G Oil LLC · Section with this well →
| Cisco | 740 | |
| Gunsight | 1,930 | |
| Gunsight | 1,960 | |
| Vogstberger | — | |
| KMA | — | |
| Strawn | — | |
| Tannehill | — | |
| Bluff Creek Sand | — |
10 TOPS · FIRST 8
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/48546298, documented in the API reference.