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

King Ranch West Borregos #M113

Plugged

Kleberg County · Borregos West (F-53 North) field  · Vertical

Fields on the latest permit · any of 2
Borregos, West (F-53, North) · Borregos W. (F- 90)
Not one formation; the well must be completed in one of them, and no target formation is stated. The district's wildcat field is also on the permit.

King Ranch West Borregos #M113 (API 42-273-31991) is a plugged well in Kleberg County, plugged January 10, 2011, last operated by Exxon Mobil Corporation.

The RRC has issued 5 drilling permits (amended twice) between 1985 and 1995, permitted to 7,550 ft.

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

Its 4 leases have reported 110 barrels of oil and 270K mcf of gas since the record begins in January 1993, with no volume in the three years through August 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

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleExxon Mobil Corporation
Production reportsExxon Mobil Corporationthrough May 2006
Latest permitExxon Corp.Sep 8, 1995

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

7,550
total depth, ft
7
permits on file
Sep 8, 1995
last permit issued
Dec 5, 1995
completed
110
cumulative oil, bbl
270K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · JAN 1996 THROUGH MAY 2006

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 5, 1995
Shut in
—
Plugged
Jan 10, 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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH AUG 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 West Borregos G-4-158005Borregos, West (F-53, North)Exxon Mobil Corporation1110270KDec 1995 – May 2006
King Ranch West Borregos G-4-137405Borregos, W. (G-11)Exxon Corp.100by Jan 1993 – —
— O-4-10798——000—
King Ranch West Borregos O-4-10962Borregos, West (F-53, North)Exxon Mobil Corporation200by Jan 1993 – —

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

Wells named King Ranch West Borregos

Exxon Mobil Corporation's other wells filed under this lease name in Kleberg County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Exxon Corp.Jan 1996 → Nov 1998
  2. 2Exxon Mobil CorporationApr 2005 → May 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
439718-98RecompletionExxon Corp.Feb 22, 1996Sep 8, 1995Nov 30, 19956,026
439718-99RecompletionExxon Corp.Sep 8, 1995Sep 8, 1995—6,026
374836-98RecompletionExxon Corp.Jan 29, 1991Jun 26, 1990Dec 13, 19907,550
374836-99RecompletionExxon Corp.Jun 25, 1990Jun 26, 1990—7,550
341048-99RecompletionExxon Corp.Jan 6, 1988Jan 7, 1988—7,550
292017-99RecompletionExxon Corp.Nov 27, 1985Dec 2, 1985—6,550
272121-99DrillExxon Corp.Apr 12, 1985Apr 12, 1985Apr 14, 19857,550

Completions

CompletedLeaseFieldOperatorStatusDepth
Dec 5, 1995King Ranch West Borregos G-4-158005Borregos West (F-53 North)Exxon Mobil CorporationPlugged—
Dec 31, 1990King Ranch West Borregos G-4-137405Borregos W. (G-11)Exxon Corp.Plugged—
Dec 27, 1985King Ranch West Borregos O-4-10962Borregos West (F-53 North)Exxon Mobil CorporationPlugged—
May 2, 1985King Ranch West Borregos O-4-10798Borregos West (G-49 N.)Exxon Corp.Plugged—

Perforations

Perforated and open-hole intervals.

FromToType
5,3305,352Perforated
5,5005,515Perforated
6,1336,137Perforated
6,4836,488Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,29712.25650 S
8.6251,29712.5650 S
8.6251,298——
2.8756,5167.875602 S
2.8756,516——
2.8756,5197.875602 S
2.8756,546——

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
00Jun 11, 1996Feb 26, 1996Yes
00May 24, 1996——
00Aug 9, 1991Feb 6, 1991Yes
00Mar 28, 1991——
00Feb 19, 1986Feb 4, 1986Yes
00Feb 12, 1986——
00Jul 18, 1985May 22, 1985—
00Jul 16, 1985——

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 →

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