WELL · 42-071-31248 · DISTRICT 3

RFR Tract 224 #185

N

Chambers County  · Vertical

Rfr Tract 224 #185 (API 42-071-31248) is a permitted well in Chambers County filed by Masters Oil & Gas, LLC; no completion report is on file yet.

The RRC has issued 4 drilling permits (amended once) between 1981 and 2004, permitted to 11,750 ft.

Completion filings report one formation top, including Frio.

Operator of record

Masters Oil & Gas, LLC

Houston, TX · P-5 Y, filed Dec 4, 2025 · 28 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsGalveston Bay Energy, LLCthrough Mar 2016
Latest permitMasters Oil & Gas, LLCAug 17, 2004
11,750
total depth, ft
5
permits on file
Aug 17, 2004
last permit issued
—
completed
0
cumulative oil, bbl
1.12M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 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 lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
RFR Tract 224 G-3-99996Red Fish Reef (FB a-1, Frio 22C)Galveston Bay Operating Co LLC101.12MJan 1993 – Jul 2026

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. 1Vintage Petroleum, Inc.Jan 1993 → Oct 1996
  2. 2Masters Oil & Gas, LLCJan 2005 → Jan 2006
  3. 3Tekoil and Gas Gulf Coast, LLCAug 2007 → Jun 2008
  4. 4Galveston Bay Energy, LLCJun 2010 → Mar 2016

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
549463-98RecompletionMasters Oil & Gas, LLCOct 6, 2004Aug 17, 2004—11,182
549463-99RecompletionMasters Oil & Gas, LLCAug 11, 2004Aug 17, 2004—11,182
408613-99OtherVintage Petroleum, Inc.Jan 29, 1993Jan 29, 1993Mar 13, 199411,182
383653-99RecompletionExxon Corp.Jan 21, 1991Jan 24, 1991Sep 30, 199211,182
128859-99DrillExxon Corp.Aug 6, 1981Aug 6, 1981Feb 4, 198211,750

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-99996————

Formation tops

As filed on W-2/G-1. Subsea from 21 ft elevation.Download CSV →

FormationMD ftSubsea
FrioFRIO 22A10,878-10,857
FrioFRIO 22 A10,917-10,896
FrioFRIO 22 B10,956-10,935
FrioFRIO 22B10,960-10,939
FrioFRIO 22 C11,039-11,018
FrioFRIO 22C11,039-11,018

Perforations

Perforated and open-hole intervals.

FromToType
10,87810,882Perforated
10,88810,902Perforated
10,96010,980Perforated
11,03911,061Perforated
11,04011,062Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.752,25014.752,005 S
2.37510,834——
5.511,1429.8751,990 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 →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jun 1, 1994Apr 14, 1994—
00Mar 30, 1993Nov 30, 1992Yes
00Jan 12, 1984Jun 7, 1982—

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