PERMITS · ALL ON FILE

338 Oil & Gas, Inc. permits

Newest first by issue date. A window counts the day each permit first appeared in Railroad Commission daily files, which runs a few days behind. How permits work →

15 permits match

17 FILINGS · 15 PERMITS · PAGE 1 OF 1

On the mapSave this search
PermitSeenIssuedOperatorCountyLease / wellDepthAPI
804272Mar 6, 2015Mar 6, 2015338 Oil & Gas, Inc.BexarSpeedway Unit 1 #11,60002938338
793819Sep 15, 2014Sep 15, 2014338 Oil & Gas, Inc.MedinaErnest #22,50032534116
789064Jul 21, 2014Jul 21, 2014338 Oil & Gas, Inc.MedinaBond #111,25032532473
789060Jul 21, 2014Jul 21, 2014338 Oil & Gas, Inc.MedinaBond #101,17532532469
789048Jul 21, 2014Jul 21, 2014338 Oil & Gas, Inc.MedinaBond #91,25032532470
770114Sep 24, 2013Sep 24, 2013338 Oil & Gas, Inc.MedinaErnest #12,50032534061
770114AmendmentSep 24, 2013Sep 24, 2013338 Oil & Gas, Inc.MedinaErnest #12,50032534061
767300Aug 9, 2013Aug 9, 2013338 Oil & Gas, Inc.MedinaBond #221,22032532362
767220Aug 6, 2013Aug 6, 2013338 Oil & Gas, Inc.MedinaPierce #31,20032534013
753329Dec 27, 2012Dec 27, 2012338 Oil & Gas, Inc.MedinaFloyd C. Bond #201,21332532484
737116Apr 26, 2012Apr 26, 2012338 Oil & Gas, Inc.MedinaPierce #221,20432532602
737115Apr 26, 2012Apr 26, 2012338 Oil & Gas, Inc.MedinaBond #680032501231
737115AmendmentApr 26, 2012Apr 26, 2012338 Oil & Gas, Inc.MedinaBond #61,20032501231
729636Dec 15, 2011Dec 15, 2011338 Oil & Gas, Inc.MedinaBond #261,21432532574
729635Dec 15, 2011Dec 15, 2011338 Oil & Gas, Inc.MedinaBond #251,20432532573
723712Sep 8, 2011Sep 8, 2011338 Oil & Gas, Inc.MedinaBond #21,10032533798
719675Jul 7, 2011Jul 7, 2011338 Oil & Gas, Inc.MedinaBond #11,50032533794

About this data

Drilling permits from the RRC OGA049M master and the daily daf420 files, keyed on the day each permit first appeared in those files. Operator names as filed; application types per the RRC code table.

New to these records? how permits work · why the window is on first-seen

Developers: this page as JSON is GET /v1/data/permits/tx, documented in the API reference.