LEASES · PDQ LEASE REPORTS
Leases reported by Blue Wing Energy, Inc.
Oil is reported by lease, not by well. Every lease with a production report, with its reporting operator, field, well count, and lifetime volumes. Oil includes condensate from gas leases and gas includes casinghead gas from oil leases, as the RRC totals them. How production is reported →
10 leases match
10 LEASES · PAGE 1 OF 1
| Lease | Operator | Field | County | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|---|
| Borchers Estate G-2-78981 | Blue Wing Energy, Inc. | Borchers, South (1300) | Lavaca | 1 | 0 | 0 | — |
| Borchers G-2-102632 | Blue Wing Energy, Inc. | Borchers (1370) | Lavaca | 1 | 0 | 0 | — |
| Borchers Estate G-2-105820 | Blue Wing Energy, Inc. | Borchers (1370) | Lavaca | 1 | 0 | 80.9K | Oct 2007 – Feb 2024 |
| Borchers Estate G-2-131569 | Blue Wing Energy, Inc. | Borchers (2200) | Lavaca | 1 | 0 | 222K | by Jan 1993 – Feb 2006 |
| Borchers Estate G-2-144646 | Blue Wing Energy, Inc. | Borchers (3070) | Lavaca | 1 | 0 | 803K | Feb 1993 – Dec 2006 |
| Borchers Estate G-2-167856 | Blue Wing Energy, Inc. | Borchers (3250) | Lavaca | 1 | 0 | 67.4K | Mar 1998 – Aug 2025 |
| Borchers Estate G-2-226811 | Blue Wing Energy, Inc. | Borchers (2130) | Lavaca | 1 | 0 | 392K | Jan 2007 – Feb 2024 |
| Borchers Estate G-2-227972 | Blue Wing Energy, Inc. | Borchers (2100) | Lavaca | 1 | 0 | 334K | Feb 2007 – Feb 2024 |
| Borchers Estate G-2-241168 | Blue Wing Energy, Inc. | Borchers (2100) | Lavaca | 1 | 0 | 2.32K | Dec 2007 – Feb 2024 |
| Borchers, William -B- G-2-254697 | Blue Wing Energy, Inc. | Borchers (3800) | Lavaca | 1 | 0 | 1.19K | Apr 2017 – Mar 2024 |
About this data
Lease summaries from the RRC PDQ production dump: lifetime oil, gas, and casinghead, well count from completion reports, and the first and last month with a report. Lease reports leave the county blank; the county shown is the one the lease's completed wells are in, rebuilt nightly.
Developers: this page as JSON is GET /v1/data/leases/tx, documented in the API reference.