WELLS · TEXAS · ONE ROW PER API NUMBER

Charro Operating L.L.C. wells in Refugio County

Every well on the Railroad Commission's schedule or with a drilling permit on file, newest permit first: who operates it, where it is, the field it is completed in, its permits, and the last month its lease reported.What an API number is →

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

Texas reports production by lease, so a well carries no volumes of its own: "Last reported" is the last month the lease it is tied to reported. How Texas production is reported →

26 WELLS · PAGE 1 OF 1

These wells on a map →
WellOperatorCounty, fieldStatusDepth, ftPermitPermitsLast reported
Reilly #142-391-33212Charro Operating L.L.C. RefugioPhil Power (5200)ActiveGas5,850Jul 29, 20191Apr 2026
Vidauri F #2542-391-32858Charro Operating L.L.C. RefugioGreta North (6500 Sd.)ActiveGas7,100Sep 28, 20173Apr 2026
Welder Heirs TC #142-391-33178Charro Operating L.L.C. RefugioGreta North (6440)PluggedGas7,200Aug 30, 20171Apr 2019
Welder Heirs - CM #342-391-33156Charro Operating, L.L.C. RefugioNot on schedule6,950Nov 23, 20151—
Shay B #242-391-32186Charro Operating L.L.C. RefugioPhil Power North (Miocene A)PluggedGas6,500Apr 30, 20155Dec 2017
Vidauri a #142-391-32674Charro Operating L.L.C. RefugioPhil Power (5000)PluggedGas6,300Nov 10, 20103May 2015
Vidauri E #4442-391-32967Charro Operating L.L.C. RefugioPhil Power (5100)PluggedGas6,200Aug 4, 20101Nov 2010
M.V. O Connor Estate E #542-391-32906Charro Operating L.L.C. RefugioGreta (F-2-A)PluggedGas5,700May 26, 20092Aug 2011
M.V. O Connor Estate E #2042-391-32907Charro Operating L.L.C. RefugioGreta (5270)PluggedGas5,700May 26, 20092Oct 2009
Vidauri F #3442-391-32889Charro Operating L.L.C. RefugioGreta North (6300 Frio)PluggedGas7,700Dec 8, 20082Oct 2012
Vidauri P #3142-391-32885Charro Operating L.L.C. RefugioPhil Power (5000)PluggedGas6,500Nov 15, 20081Dec 2011
Vidauri F #2642-391-32878Charro Operating L.L.C. RefugioPhil Power (5550)PluggedGas7,000Oct 28, 20081Apr 2011
Blanca Shay #142-391-32872Charro Operating L.L.C. RefugioGaffney (5540 N W)PluggedGas6,300Oct 15, 20082Feb 2019
O Connor M.V. Estate C #742-391-32862Charro Operating L.L.C. RefugioTrain Wreck (5500)PluggedGas7,000Aug 28, 20081Jul 2010
Vidauri G #2442-391-32857Charro Operating L.L.C. RefugioPhil Power (5100)PluggedGas6,500Jul 25, 20081Jul 2011
Vidauri E #1342-391-32845Charro Operating L.L.C. RefugioVidauri SW. (5100)PluggedGas8,000May 6, 20082May 2013
Vidauri D #842-391-32840Charro Operating L.L.C. RefugioPhil Power (5200-B)PluggedGas8,000Apr 15, 20083Jul 2009
Vidauri F #1042-391-32839Charro Operating L.L.C. RefugioVidauri (5800)PluggedGas8,000Apr 12, 20082Jun 2019
Vidauri "G" #2242-391-32837Charro Operating, L.L.C. RefugioNot on schedule4,000Apr 3, 20081—
Vidauri G #1142-391-32829Charro Operating L.L.C. RefugioWildcatPluggedGas4,000Mar 14, 20082Jun 2008
M.V.O.C.-Baptist Unit #142-391-32802Charro Operating L.L.C. RefugioBlanco Creek (6400)PluggedOil7,200Dec 15, 20071Mar 2016
Vidauri #942-391-32773Charro Operating L.L.C. RefugioVidauri (5800)PluggedGas6,200May 25, 20071May 2011
Vidauri E #742-391-32770Charro Operating L.L.C. RefugioPhil Power (5200)Shut inOil6,150May 21, 20072Nov 2024
O Connor M. V. Estate C #642-391-32754Charro Operating L.L.C. RefugioTrain Wreck (6000 Sd.)PluggedGas6,600Nov 28, 20061Jan 2016
O Connor M. V. Estate #1A42-391-32751Charro Operating L.L.C. RefugioWildcatPluggedGas6,200Nov 9, 20061—
Mercy Hosptal-Huff Unit #142-391-32747Charro Operating L.L.C. RefugioAgnes Barber (Frio 5500)PluggedOil6,200Oct 12, 20061—

About this data

One row per API number: every well on the Railroad Commission wellbore schedule, and every API number a drilling permit names. Operator, field, status, and dates are the schedule's where it lists the well, the latest permit's otherwise. Permits on file counts every permit and amendment. Texas reports production by lease, so a well shows the last month its lease reported and no volumes. Nothing is estimated.

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