WELL · 42-485-44281 · DISTRICT 9
Seay E #4R
Wichita County · K-M-A field · Vertical
Seay E #4R (API 42-485-44281) is a permitted well in Wichita County filed by Keirus, Inc.; no completion report is on file yet.
The RRC has issued one drilling permit, issued August 28, 2007, permitted to 2,000 ft.
Completion filings report one formation top, including Thomas Sand.
Its 2 leases have reported 69K barrels of oil and 56.1K mcf of gas since March 2006, last reporting in July 2026. The leases carry 4 wells, so these are lease totals, not this well alone.
Operator of record
Wichita Falls, TX · P-5 Y, filed Jul 4, 2026 · 4 permits on file · (940) 782-7528
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Keirus Inc. |
| Production reports | Keirus, Inc.through Apr 2026 |
| Latest permit | Keirus, Inc.Aug 28, 2007 |
- 2,000
- total depth, ft
- 1
- permits on file
- Aug 28, 2007
- last permit issued
- —
- completed
- 69K
- cumulative oil, bbl
- 56.1K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Mar 2006 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
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 2 leases 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 |
|---|---|---|---|---|---|---|
| Seay E O-13-30661 | K-M-A | Keirus, Inc. | 2 | 43K | 38.1K | Mar 2006 – Jul 2026 |
| Seay E O-13-31082 | Wichita County Regular | Keirus, Inc. | 2 | 26K | 18K | Nov 2007 – Jul 2026 |
Oil, barrels lease total
Last 12 months 1,850 · prior 12 2,155(-14%)
Gas, mcf lease total
Last 12 months 0 · prior 12 396(-100%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Rusk Production Inc.Jun 2006 → Sep 2006
- 2Keirus, Inc.Oct 2006 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 642958-99 | Drill | Keirus, Inc. | Jul 20, 2007 | Aug 28, 2007 | Sep 24, 2007 | 2,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-13-30661 | — | — | — | — |
| — | — O-13-31082 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 1,646 | 1,650 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 4.5 | 1,852 | 7.875 | 375 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 | Dec 4, 2009 | Nov 13, 2007 | Yes |
| 00 | Oct 14, 2009 | — | — |
| 00 | Aug 28, 2009 | — | — |
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-44281 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-485-44281 → 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/48544281, documented in the API reference.