WELL · 42-431-31495 · DISTRICT 8

Barbee -B- #105

N

Sterling County · Conger (Penn) field  · Vertical

Barbee -B- #105 (API 42-431-31495) is a well in Sterling County operated by Wagner & Brown, completed August 7, 1984.

The RRC has issued one drilling permit, issued June 26, 1984, permitted to 8,500 ft.

Completion filings report 6 formation tops, including Seven Rivers, Queen, Grayburg, San Andres.

No lease production has been reported under this well’s leases.

Operator of record

Wagner & Brown

Based in
Midland, TX
P-5 status
Inactive (I)
P-5 last filed
Dec 3, 1992
Permits on file
583
Phone
(432) 682-7936

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWagner & Brown
Production reportsBurk Royalty Co., Ltd.through Aug 2025
Latest permitWagner & BrownJun 26, 1984

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

8,500
total depth, ft
1
permits on file
Jun 26, 1984
last permit issued
Aug 7, 1984
completed
0
cumulative oil, bbl
265K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 7, 1984
Shut in
—
Plugged
—

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Barbee "B" G-10-113424Conger (Penn)Burk Royalty Co., Ltd.10265KJan 1993 – Jul 2026

Gas, mcf lease total

Last 12 months 527 · prior 12 1,748(-70%)

0100200300202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Wagner & Brown, Ltd.Jan 1993 → Dec 2003
  2. 2Range Production CompanyJan 2004 → Jul 2014
  3. 3EQT Production Texas, LLCAug 2014 → Jun 2018
  4. 4Stanolind Production LLCJul 2018 → Dec 2020
  5. 5Slant Operating, LLCJan 2021 → Dec 2021
  6. 6Burk Royalty Co., Ltd.Jan 2022 → Aug 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
243233-99DrillWagner & BrownJun 26, 1984Jun 26, 1984—8,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-10-113424————

Formation tops

As filed on W-2/G-1. Subsea from 2,547 ft elevation.Download CSV →

FormationMD ftSubsea
Seven Rivers7 RIVERS1,2191,328
Queen1,587960
Grayburg1,840707
San Andres1,976571
Cisco7,376-4,829
Canyon7,462-4,915

Perforations

Perforated and open-hole intervals.

FromToType
7,5207,553Perforated
7,6457,822Perforated
—7,553Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,90012.251,200 S
4.58,0107.875350 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jan 16, 1985Nov 12, 1984—
00Nov 16, 1984Oct 2, 1984—
00Sep 26, 1984Sep 13, 1984—
00Sep 6, 1984Sep 13, 1984—
00Sep 5, 1984Sep 13, 1984—

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

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