OPERATORS · TEXAS · P-5 NUMBER 728874 · MARTIN COUNTY

Rosewood Resources, Inc. in Martin County

One operator, one county: its permits, wells of record, formations, and leases here, with the rest of the county and the rest of the operator one click away.

Rosewood Resources, INC. has 11 drilling permits on file in Martin County, the first issued in 1984 and the latest on February 14, 1990.

None were issued in the last twelve months.

It is operator of record on 2 wells in the county: 0 producing, 0 shut in, 0 injection.

Its completed wells here most often report Chester, Mississippian, Spraberry.

0
permits, 12 months
11
permits, all time since 1984
—
horizontal, 12 months
—
ft average depth, 12 months
2
wells of record
0
producing · 0 shut in · 0 injection

Permits issued by month

LAST FIVE YEARS · MARTIN ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Feb 14, 1990Shaw #2045 369750Drill10,000
Dec 13, 1988Davis #5046 353154Drill10,500
Nov 9, 1988Davis #6046 353185Drill11,000
Nov 7, 1988Davis #5046 351485Drill10,500
Jul 5, 1988Peters Estate #103 348396Drill12,000
Mar 2, 1988Davis #4046 343341Drill10,000
Jul 23, 1987Davis #3046 333052Drill10,800
Nov 26, 1986Davis #2046 323501Drill10,000
May 6, 1986Davis #1046 301850Drill10,700
Apr 8, 1986Shepard #1028 300743Drill11,000

All 11 permits in Martin County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Drill
0 / 11

12 MONTHS / ALL TIME

Leases it reports here

No leases with wells completed in this county carry this operator's production reports.

All leases it reports → ·  Other operators in Martin County →

About this data

Permits from the RRC OGA049M master and daily daf420 files; wells of record and status from the EWA wellbore schedule, weekly; formations from the dbf900 wellbore file; leases from PDQ lease reports, placed in the county by the wells completed on them.

Developers: this page as JSON is GET /v1/data/operators/tx/728874/counties/martin, documented in the API reference.