WELLS · UNITED STATES · ONE ROW PER API NUMBER

Berry Oil Comp. wells in Glasscock County

Every well on file in every state Petrora holds. Narrow it to a state, a county, an operator, or the formation the well is completed in.What an API number is →

A full API number opens the well. Anything else filters the list below.

34 WELLS · PAGE 1 OF 1

These wells on a map →
WellOperatorCounty, field or poolStatusDepth, ftPermitOil, 12 moGas, 12 mo
Zant 47 SWD #142-173-31781Berry Oil Comp. Glasscock, TXSpraberry (Trend Area)Plugged10,500Apr 30, 2014——
Zant #371042-173-36259Berry Oil Comp. Glasscock, TXNot on schedule12,000Jan 9, 2014——
Blalock F #1WS42-173-35255Berry Oil Comp. Glasscock, TXSanta Rosa (Tansil)Not on schedule1,100Aug 21, 2012——
Zant #2WS42-173-35257Berry Oil Comp. Glasscock, TXSanta Rosa (Tansil)Not on schedule1,100Aug 21, 2012——
Zant C #350442-173-35089Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 31, 2012——
Blalock D #11642-173-35025Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 18, 2012——
Blalock a #481342-173-35026Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 18, 2012——
Zant #470942-173-35003Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 12, 2012——
Zant #471242-173-35004Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 12, 2012——
Zant #471442-173-35005Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 12, 2012——
Zant #470642-173-35006Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 12, 2012——
Zant #471542-173-35007Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 12, 2012——
Zant #380942-173-35010Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 12, 2012——
Zant #380842-173-35011Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 12, 2012——
Zant #370942-173-35012Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 12, 2012——
Zant #370742-173-35013Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 12, 2012——
Zant #380342-173-35009Berry Oil Comp. Glasscock, TXNot on schedule12,000May 24, 2012——
Zant #370442-173-34998Berry Oil Comp. Glasscock, TXNot on schedule12,000May 23, 2012——
Zant #110342-173-34997Berry Oil Comp. Glasscock, TXNot on schedule12,000May 22, 2012——
Zant #380642-173-34993Berry Oil Comp. Glasscock, TXNot on schedule12,000May 21, 2012——
Zant #110242-173-34994Berry Oil Comp. Glasscock, TXNot on schedule12,000May 21, 2012——
Zant #370142-173-34995Berry Oil Comp. Glasscock, TXNot on schedule12,000May 21, 2012——
Berry #200442-173-34669Berry Oil Comp. Glasscock, TXNot on schedule12,000Jan 26, 2012——
Zant C #350342-173-34719Berry Oil Comp. Glasscock, TXNot on schedule12,000Jan 13, 2012——
Zant #20342-173-34709Berry Oil Comp. Glasscock, TXNot on schedule12,000Jan 9, 2012——
Berry #200342-173-34667Berry Oil Comp. Glasscock, TXNot on schedule12,000Jan 4, 2012——
Berry #210342-173-34670Berry Oil Comp. Glasscock, TXNot on schedule12,000Jan 4, 2012——
Berry #210442-173-34671Berry Oil Comp. Glasscock, TXNot on schedule12,000Dec 21, 2011——
Blalock a #480142-173-34672Berry Oil Comp. Glasscock, TXNot on schedule12,000Dec 21, 2011——
Zant #471042-173-34373Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 20, 2011——
Zant #380142-173-34356Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 14, 2011——
Zant #380542-173-34357Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 14, 2011——
Zant #370342-173-34345Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 6, 2011——
Zant #370542-173-34348Berry Oil Comp. Glasscock, TXNot on schedule12,000Jul 6, 2011——

OIL IN BBL · GAS IN MCF · TWELVE MONTHS THROUGH THE STATE'S REPORTED-THROUGH MONTH · A DASH MEANS NO PRODUCTION BY WELL IS AVAILABLE FOR THE STATE

About this data

One row per API number from each state regulator's records, in one shared shape. Status and type are shown in the regulator's own words; the filters use one vocabulary. A well is tied to a formation through the field or pool it is completed in. Volumes appear where a state reports production by well, summed over the twelve months ending in that state's last reported month. Nothing is estimated.

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