WELL · 42-055-33416 · DISTRICT 1
Denison #2
Caldwell County · Salt Flat field · Vertical
Denison #2 (API 42-055-33416) is a plugged well in Caldwell County, plugged May 1, 2003, last operated by R & S Oil Production CO..
The RRC has issued one drilling permit, issued September 27, 1983, permitted to 2,900 ft.
It was permitted by Biggs & Hill and has since transferred to R & S Oil Production CO. on the wellbore schedule.
Its lease has reported 9 barrels of oil and 2.85K mcf of gas since January 1993, last reporting in March 2008.
Operator of record
Permitted by Biggs & Hill; the EWA schedule now lists a different operator.
Luling, TX · P-5 Y, filed Jun 4, 2026 · 24 permits on file · (830) 263-0532
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | R & S Oil Production Co. |
| Production reports | R & S Oil Production Co.through Nov 1995 |
| Latest permit | Biggs & HillSep 27, 1983 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 2,900
- total depth, ft
- 1
- permits on file
- Sep 27, 1983
- last permit issued
- Nov 14, 1983
- completed
- 9
- cumulative oil, bbl
- 2.85K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2008
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Nov 14, 1983
- Shut in
- —
- Plugged
- May 1, 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; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Denison O-1-9327 | Salt Flat | R & S Oil Production Co. | 1 | 9 | 2.85K | Jan 1993 – Mar 2008 |
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.
- 1R & S Oil Production Co.Jan 1993 → Sep 1993
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 215218-99 | Drill | Biggs & Hill | Sep 27, 1983 | Sep 27, 1983 | — | 2,900 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-1-9327 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,480 | 2,710 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 81 | 12.25 | 60 S |
| 2.375 | 2,431 | — | — |
| 15.5 | 2,730 | 7.875 | 383 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jan 12, 1984 | Dec 15, 1983 | — |
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-055-33416 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-055-33416 → scanned completion filings
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/05533416, documented in the API reference.