Petrora

TEXAS · WELLS · KLEBERG COUNTY · API 42-273-00129 · DISTRICT 04

King Ranch Borregos #181

Plugged

Kleberg County · Borregos (Consolidated Gas) field  · Vertical

King Ranch Borregos #181 (API 42-273-00129) is a plugged well in Kleberg County, plugged June 15, 2000, last operated by Exxon Mobil Corporation.

The RRC has issued 5 drilling permits between 1977 and 1986, permitted to 6,993 ft.

It was permitted by Exxon Corp. and has since transferred to Exxon Mobil Corporation on the wellbore schedule.

Its 4 leases have reported 278 barrels of oil and 220K mcf of gas since January 1993, with no volume in the three years through April 2026. The leases carry 4 wells, so these are lease totals, not this well alone.

Operator of record

Exxon Mobil Corporation

Permitted by Exxon Corp.; the EWA schedule now lists a different operator.

Based in
Spring, TX
P-5 status
Active (A)
P-5 last filed
Jul 15, 2026
Permits on file
1,223
Phone
(346) 474-9142
Watch this operatorWatch Kleberg County

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleExxon Mobil Corporation
Production reportsExxon Mobil Corporationthrough Apr 1997
Latest permitExxon Corp.Feb 27, 1986

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

6,993
total depth, ft
5
permits on file
Feb 27, 1986
last permit issued
May 6, 1997
completed
278
cumulative oil, bbl
220K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 1997

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 6, 1997
Shut in
—
Plugged
Jun 15, 2000

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 4 leases this well is completed on; they carry 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
King Ranch Borregos G-4-120998Borregos (Consolidated Gas)Exxon Mobil Corporation12527KJan 1993 – Apr 1997
King Ranch Borregos G-4-38958Borregos (Zone N-17)Exxon Corp.1252187KJan 1993 – May 1995
King Ranch Borregos G-4-63038Borregos (Zone H-3)Exxon Corp.116.21KJan 1993 – Oct 1993
King Ranch Borregos G-4-50452Borregos (Zone P-3, N.)Exxon Corp.100Jan 1993 – —

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1Exxon Corp.Jan 1993 → Apr 1997

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
299227-99RecompletionExxon Corp.Feb 26, 1986Feb 27, 1986—6,993
290361-99RecompletionExxon Corp.Nov 15, 1985Nov 18, 1985—6,993
265839-99RecompletionExxon Corp.Jan 31, 1985Feb 1, 1985—6,993
186328-99RecompletionExxon Corp.Feb 17, 1983Feb 17, 1983Mar 18, 19836,993
11757-99OtherExxon Corp.Nov 8, 1977Nov 8, 1977—6,993

Completions

CompletedLeaseFieldOperatorStatusDepth
May 6, 1997King Ranch Borregos G-4-120998Borregos (Consolidated Gas)Exxon Mobil CorporationPlugged—
Jun 11, 1985King Ranch Borregos G-4-50452Borregos (Zone P-3 N.)Exxon Corp.Plugged—
Jun 29, 1983King Ranch Borregos G-4-79151Borregos (Zone L-9 & 11)Exxon Corp.Plugged—
Jun 29, 1983King Ranch Borregos G-4-79151Borregos (Zone L-9 & 11)Exxon Corp.Plugged—
Dec 23, 1974King Ranch Borregos G-4-63038Borregos (Zone H-3)Exxon Corp.Plugged—
—King Ranch Borregos G-4-38958Borregos (Zone N-17)Exxon Corp.Plugged—
—Borregos K. R. & Seeligson O-4-6544Borregos (Combined Zones)EOG Resources Inc.Plugged—

Perforations

Perforated and open-hole intervals.

FromToType
4,6844,694Perforated
4,7374,757Perforated
4,7864,803Perforated
5,0105,358Perforated
5,0125,054Perforated
5,1485,166Perforated
5,4705,482Perforated
5,5435,553Perforated
5,5436,273Perforated
5,6765,682Perforated
5,7305,740Perforated
5,9505,958Perforated
5,9505,962Perforated
6,0726,080Perforated
6,2056,217Perforated
6,2666,273Perforated
6,3926,428Perforated
6,7976,818Perforated
—6,889Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37535——
13.37565——
10.751,455——
10.751,50315960 S
13.3751,50415960 S
10.751,50415960 S
2.8755,990——
2.8756,980—100 S
2.8756,9809.8751,000 S
2.8756,9909.875100 S
2.8756,990——
—6,990——
2.8756,993——
—6,993——
10.7515,03415960 S
10.75———

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 →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00May 30, 1997May 14, 1997—
00Mar 28, 1997Feb 6, 1997—
00Apr 12, 1996Mar 11, 1996—
00May 20, 1986May 2, 1986Yes
00May 14, 1986——
00Nov 27, 1985Nov 4, 1985—
00Feb 11, 1985Jan 14, 1985—
00Jan 12, 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.

Log images filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

Find logs withinmiles of this well:List →Map →

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
0
bbl, all reported
—
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000095616UIC PermitPlugged Jun 15, 2000006,755–6,779

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