WELL · 42-049-35833 · DISTRICT 7

Newman #1

Y

Brown County · Brown County Regular field · Producing  · Vertical

Newman #1 (API 42-049-35833) is a well in Brown County operated by 4 J S Production, completed February 6, 2006 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued October 27, 2005, permitted to 4,000 ft.

It was permitted by Couch, Gilbert and has since transferred to 4 J S Production on the wellbore schedule.

Completion filings report 3 formation tops, including Caddo, Marble Falls, Barnett.

Its lease has reported 11.9K barrels of oil and 24.5K mcf of gas since February 2006, last reporting in July 2026. The lease carries 6 wells, so these are lease totals, not this well alone.

Operator of record

4 J S Production

Permitted by Couch, Gilbert; the EWA schedule now lists a different operator.

Zephyr, TX · P-5 Y, filed Aug 4, 2025 · 20 permits on file · (325) 200-2826

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedule4 J S Production
Production reports4 J's Productionthrough Apr 2026
Latest permitCouch, GilbertOct 27, 2005

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

4,000
total depth, ft
1
permits on file
Oct 27, 2005
last permit issued
Feb 6, 2006
completed
11.9K
cumulative oil, bbl
24.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2006 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 6, 2006
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Newman O-8-29692Brown County Regular4 J's Production611.9K24.5KFeb 2006 – Jul 2026

Oil, barrels lease total

Last 12 months 155 · prior 12 194(-20%)

0204060202420252026

Chain of custody

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

  1. 1Couch, GilbertFeb 2006 → Jul 2013
  2. 24 J's ProductionAug 2013 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
608374-99DrillCouch, GilbertOct 24, 2005Oct 27, 2005Nov 5, 20054,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-29692————

Formation tops

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

FormationMD ftSubsea
Caddo1,590-236
Marble Falls1,625-271
BarnettBARNETT SHALE1,714-360

Perforations

Perforated and open-hole intervals.

FromToType
1,6341,660Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62535711145 S
4.51,7966.7570 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
00Sep 5, 2006Feb 17, 2006Yes
00Mar 30, 2006——

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