WELL · 42-083-31396 · DISTRICT 7

Bartholomew G. B. #19

Plugged

Coleman County · Coleman County Regular field  · Vertical

Bartholomew G. B. #19 (API 42-083-31396) is a plugged well in Coleman County, plugged June 2, 2003, last operated by MY Hop Mineral.

The RRC has issued one drilling permit, issued February 24, 1978, permitted to 1,700 ft.

It was permitted by D & B Oil Inc. and has since transferred to MY Hop Mineral on the wellbore schedule.

Its lease has reported 1.07K barrels of oil and 50 mcf of gas since January 1993, last reporting in July 2026. The lease carries 15 wells, so these are lease totals, not this well alone.

Operator of record

MY Hop Mineral

Permitted by D & B Oil Inc.; the EWA schedule now lists a different operator.

Moorhead, MN · P-5 Y, filed Oct 6, 2006 · 1 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMY Hop Mineral
Production reportsMY Hop Mineralthrough Jun 1998
Latest permitD & B Oil Inc.Feb 24, 1978

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

1,700
total depth, ft
1
permits on file
Feb 24, 1978
last permit issued
Jan 8, 1981
completed
1.07K
cumulative oil, bbl
50
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 8, 1981
Shut in
—
Plugged
Jun 2, 2003

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; they carry 15 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bartholomew, G. B. O-8-820Coleman County RegularMY Hop Mineral151.07K50Jan 1993 – Jul 2026

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1Rice, James D.Jan 1993 → Mar 1995
  2. 2MY Hop MineralApr 1995 → Apr 1996

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
18905-99DrillD & B Oil Inc.Feb 24, 1978Feb 24, 1978Mar 30, 19781,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-820————

Perforations

Perforated and open-hole intervals.

FromToType
1,4421,450Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
2.3751,450——
4.51,5687.875325 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 12, 1984Jun 26, 1978—

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

480
bbl, last 12 reported months
60.3K
bbl, all reported
Mar 1997
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000044245H-1 InjectionPlugged Jul 8, 20035005001,442–1,450

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 480 · prior 12 3,000(-84%)

020040060019961997

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/08331396, documented in the API reference.