TEXAS · WELLS · MONTGOMERY COUNTY · API 42-339-30751 · DISTRICT 03
Conroe Field Unit #1949
Montgomery County · Conroe field · Producing · Vertical
Conroe Field Unit #1949 (API 42-339-30751) is a well in Montgomery County operated by Highmark Energy Operating LLC, completed May 5, 2022 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued February 19, 1986, permitted to 5,302 ft.
It was permitted by Exxon Corp. and has since transferred to Highmark Energy Operating LLC on the wellbore schedule.
Completion filings report 8 formation tops, including 2nd Upper Cockfield, Moody'S Branch, Moody'S Brance, 1st Upper Cockfield.
Its 2 leases have reported 26.7M barrels of oil and 61.7M mcf of gas since January 1993, last reporting volume in April 2026. The leases carry 665 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Exxon Corp.; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Mar 9, 2026
- Permits on file
- 23
- Phone
- (469) 214-5299
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Highmark Energy Operating LLC |
| Production reports | Highmark Energy Operating, LLCthrough Apr 2026 |
| Latest permit | Exxon Corp.Feb 19, 1986 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 5,302
- total depth, ft
- 1
- permits on file
- Feb 19, 1986
- last permit issued
- May 5, 2022
- completed
- 26.7M
- cumulative oil, bbl
- 61.7M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- May 5, 2022
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
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 2 leases this well is completed on; they carry 665 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Conroe Field Unit O-3-11659 | Conroe | Highmark Energy Operating, LLC | 664 | 26.7M | 61.4M | Jan 1993 – Apr 2026 |
| Conroe Field Unit G-3-168338 | Conroe | Denbury Onshore, LLC | 1 | 1.33K | 324K | May 1998 – May 2008 |
Oil, barrels lease total
Last 12 months 528,577 · prior 12 506,957(+4%)
Gas, mcf lease total
Last 12 months 174,487 · prior 12 323,330(-46%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Exxon Corp.Jan 1993 → Mar 2000
- 2Exxon Mobil CorporationApr 2000 → Aug 2006
- 3Wapiti Operating, LLCSep 2006 → Dec 2009
- 4Denbury Onshore, LLCJan 2010 → Oct 2024
- 5Highmark Energy Operating, LLCNov 2024 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 298158-99 | Drill | Exxon Corp. | Feb 12, 1986 | Feb 19, 1986 | Mar 8, 1986 | 5,800 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| May 5, 2022 | Conroe Field Unit O-3-11659 | Conroe | Highmark Energy Operating LLC | Producing | 5,302 |
| May 8, 1998 | Conroe Field Unit G-3-168338 | Conroe | Denbury Onshore LLC | Not on Schedule | — |
Formation tops
As filed on W-2/G-1. Subsea from 163 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| 2ND Upper Cockfield | 1,861 | -1,698 |
| Moody's Branch | 4,470 | -4,307 |
| Moody's Brance | 4,770 | -4,607 |
| 1ST Upper Cockfield | 4,815 | -4,652 |
| 1ST Upper Cockfield | 4,816 | -4,653 |
| 2ND Upper Cockfield | 4,860 | -4,697 |
| 1ST Main | 4,994 | -4,831 |
| 2A | 5,043 | -4,880 |
| 2B1,2 | 5,063 | -4,900 |
| 2B3 | 5,085 | -4,922 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,815 | 4,826 | Perforated |
| 4,862 | 4,869 | Perforated |
| 5,048 | 5,058 | Perforated |
| 5,107 | 5,117 | Perforated |
| 5,112 | 5,117 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 10.75 | 1,607 | 14.75 | 1,030 S |
| 10.75 | 1,609 | 14.75 | 1,030 S |
| 7 | 5,302 | 9.875 | 575 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Aug 26, 2022 | Jul 16, 2022 | — |
| 00 | Aug 21, 2015 | Aug 18, 2015 | — |
| 00 | Jan 13, 2011 | Nov 17, 2010 | — |
| 00 | Jul 26, 2010 | May 20, 2010 | — |
| 00 | Jun 23, 1998 | Jun 4, 1998 | — |
| 00 | Jun 10, 1998 | — | — |
| 00 | Jul 27, 1988 | Jul 14, 1988 | — |
| 00 | Sep 8, 1986 | Aug 26, 1986 | Yes |
| 00 | Sep 6, 1986 | — | — |
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.
- Wellbore filings for 42-339-30751 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-339-30751 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here for it.
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/33930751, documented in the API reference.