TEXAS · WELLS · KLEBERG COUNTY · KING RANCH BORREGOS LEASE · API 42-273-30107 · DISTRICT 04
King Ranch Borregos #485
Kleberg County · Borregos (Zone R-13) field · Vertical
King Ranch Borregos #485 (API 42-273-30107) is a plugged well in Kleberg County, plugged September 8, 1994, last operated by Exxon Corp..
The RRC has issued 2 drilling permits between 1983 and 1984, permitted to 7,025 ft.
Operator of record
- Based in
- Houston, TX
- P-5 status
- See remarks (S)
- P-5 last filed
- Mar 15, 1999
- Permits on file
- 19,549
- Phone
- (713) 431-1125
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Exxon Corp. |
| Production reports | none |
| Latest permit | Exxon Corp.Jun 27, 1984 |
- 7,025
- total depth, ft
- 2
- permits on file
- Jun 27, 1984
- last permit issued
- Jan 8, 1985
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH —
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jan 8, 1985
- Shut in
- —
- Plugged
- Sep 8, 1994
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 |
|---|---|---|---|---|---|---|
| King Ranch Borregos G-4-62590 | Borregos (Zone R-13) | Exxon Corp. | 1 | 0 | 0 | Jan 1993 – — |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 243322-99 | Recompletion | Exxon Corp. | Jun 26, 1984 | Jun 27, 1984 | — | 7,025 |
| 210429-99 | Recompletion | Exxon Corp. | Aug 29, 1983 | Sep 8, 1983 | — | 7,025 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jan 8, 1985 | King Ranch Borregos G-4-62590 | Borregos (Zone R-13) | Exxon Corp. | Plugged | — |
| Jan 8, 1985 | King Ranch Borregos G-4-62590 | Borregos (Zone R-13) | Exxon Corp. | Plugged | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,811 | 5,819 | Perforated |
| 6,762 | 6,716 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,799 | 12.25 | 625 S |
| 2.875 | 7,019 | 7.875 | 690 sx |
| 2.875 | 7,219 | 7.875 | 690 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Aug 8, 1985 | Jul 25, 1985 | — |
| 00 | Jul 26, 1984 | Jun 16, 1984 | — |
| 00 | Jan 12, 1984 | Jun 16, 1984 | — |
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-273-30107 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-273-30107 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here for it.
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/27330107, documented in the API reference.