OPERATORS · TEXAS · P-5 NUMBER 742142 · LAVACA COUNTY

Sabine Oil & Gas LLC in Lavaca 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.

Sabine Oil & Gas LLC has 9 drilling permits on file in Lavaca County, the first issued in 2012 and the latest on March 20, 2014.

None were issued in the last twelve months.

It is not operator of record on any well in the county on the current wellbore schedule.

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

Permits issued by month

LAST FIVE YEARS · LAVACA ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Mar 20, 2014Kubenka Unit #1H 780243DrillHZ14,000
Mar 17, 2014Anderle Unit #1H 780239DrillHZ14,000
Mar 17, 2014Fairey Unit #1H 780239DrillHZ14,000
Jan 2, 2014Molnoskey Unit #1H 775593DrillHZ14,000
Jan 2, 2014Molnoskey Unit #1H 775593DrillHZ14,000
Dec 16, 2013Machicek Unit #1H 774952DrillHZ14,000
Oct 23, 2012Gillespie Unit #1H 750062DrillHZ13,000
Oct 23, 2012Gillespie Unit #1H 750062DrillHZ13,000
Jul 26, 2012Targac Unit #1H 744771DrillHZ13,005

All 9 permits in Lavaca County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Drill
0 / 9

12 MONTHS / ALL TIME

Formations reported

No completion tops on file for its wells here.

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 Lavaca 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/742142/counties/lavaca, documented in the API reference.