WELL · 42-337-33991 · DISTRICT 9

Bloomer #2

Plugged

Montague County · St. JO Ridge (Barnett Shale) field  · Vertical

Bloomer #2 (API 42-337-33991) is a plugged well in Montague County, plugged January 13, 2016, last operated by Eog Resources Inc..

The RRC has issued one drilling permit, issued February 2, 2008, permitted to 8,200 ft.

It was permitted by Teleo Operating, LLC and has since transferred to Eog Resources Inc. on the wellbore schedule.

Completion filings report 4 formation tops, including Strawn, Codda, Conglomerant, Barnett.

Its lease has reported 17.6K barrels of oil and 140K mcf of gas since April 2007, last reporting in May 2016. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

EOG Resources Inc.

Permitted by Teleo Operating, LLC; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Jul 4, 2026 · 16,344 permits on file · (713) 594-5431

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEOG Resources Inc.
Production reportsEOG Resources, Inc.through Jul 2015
Latest permitTeleo Operating, LLCFeb 2, 2008

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

8,200
total depth, ft
1
permits on file
Feb 2, 2008
last permit issued
Apr 18, 2008
completed
17.6K
cumulative oil, bbl
140K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2007 THROUGH May 2016

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 18, 2008
Shut in
—
Plugged
Jan 13, 2016

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 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bloomer O-13-30834St. JO Ridge (Barnett Shale)EOG Resources, Inc.217.6K140KApr 2007 – May 2016

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. 1Teleo Operating, LLCMay 2007 → Feb 2009
  2. 2EOG Resources, Inc.Mar 2009 → Feb 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
653894-99DrillTeleo Operating, LLCJan 24, 2008Feb 2, 2008Mar 5, 20088,200

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-30834————

Formation tops

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

FormationMD ftSubsea
Strawn4,166-3,060
Codda6,400-5,294
Conglomerant6,650-5,544
BarnettUPPER BARNETT7,170-6,064

Perforations

Perforated and open-hole intervals.

FromToType
7,2727,304Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,10412.25450 S
77,4428.75540 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
00Oct 9, 2008May 12, 2008Yes
00Oct 4, 2008——

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