WELL · 42-477-31060 · DISTRICT 3
Malkey #1H
Washington County · Giddings (Austin Chalk Gas) field · Producing · Horizontal
Malkey #1H (API 42-477-31060) is a horizontal well in Washington County operated by Geosouthern Operating II LLC, completed January 2, 2019 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued February 7, 2018, permitted to 14,000 ft.
Completion filings report 3 formation tops, including Caprock, Wilcox, Austin Chalk.
No lease production has been reported under this well’s leases.
Operator of record
The Woodlands, TX · P-5 Y, filed Jul 4, 2026 · 136 permits on file · (844) 733-6205
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Geosouthern Operating II LLC |
| Production reports | Geosouthern Operating II, LLCthrough Apr 2026 |
| Latest permit | Geosouthern Operating II, LLCFeb 7, 2018 |
- 14,000
- total depth, ft
- 1
- permits on file
- Feb 7, 2018
- last permit issued
- Jan 2, 2019
- completed
- 0
- cumulative oil, bbl
- 5.55M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jun 2018 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jan 2, 2019
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active
Surface location
30.168134, -96.556882
OpenStreetMap → · Google Maps →
Permit surface location from the RRC GIS record, in Washington County.
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 |
|---|---|---|---|---|---|---|
| Malkey G-3-286251 | Giddings (Austin Chalk, Gas) | Geosouthern Operating II, LLC | 1 | 0 | 5.55M | Jun 2018 – Jul 2026 |
Gas, mcf lease total
Last 12 months 234,484 · prior 12 274,688(-15%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Geosouthern Operating II, LLCJan 2019 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 835978-99 | Drill | Geosouthern Operating II, LLC | Feb 6, 2018 | Feb 7, 2018 | Feb 23, 2018 | 14,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-3-286251 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 315 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| CaprockCAPROCK - DISPOSAL | 3,252 | -2,937 |
| WilcoxWILCOX - DISPOSAL | 4,622 | -4,307 |
| Austin Chalk | 13,202 | -12,887 |
| CaprockCAPROCK - DISPOSAL | — | — |
| WilcoxWILCOX - DISPOSAL | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 13,795 | 19,462 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 1,368 | 17.5 | 910 S |
| 9.625 | 9,636 | 12.25 | 1,605 S |
| 5.5 | 19,614 | 8.5 | 1,595 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 | Jun 5, 2019 | Mar 11, 2019 | Yes |
| 00 | Apr 25, 2019 | Sep 19, 2018 | — |
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-477-31060 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-477-31060 → 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.
Nearby wells and their tops
NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM
Draw a cross-section
This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.
Prenzler42-477-31058
0.0 KM · Geosouthern Operating II, LLC · Section with this well →
| Caprock | 4,121 | -3,806 |
| Wilcox | 4,571 | -4,256 |
| Austin Chalk | 13,601 | -13,286 |
Korthauer42-477-31061
0.0 KM · Geosouthern Operating II, LLC · Section with this well →
| Caprock | 3,394 | -3,079 |
| Wilcox | 4,650 | -4,335 |
| Austin Chalk | 12,730 | -12,415 |
Double E42-477-31116
2.1 KM · Wildhorse Resources Mngt Co, LLC · Section with this well →
| Caprock | 2,410 | -1,989 |
| Wilcox | 4,618 | -4,197 |
| Pecan Gap | 11,977 | -11,556 |
| Austin Chalk | 13,185 | -12,764 |
Lehrmann42-477-31047
2.3 KM · Geosouthern Operating II, LLC · Section with this well →
| Wilcox | 4,686 | -4,356 |
| Pecan Gap | 12,222 | -11,892 |
| Austin Chalk | 12,995 | -12,665 |
| Wilcox | — | |
| Caprock | — |
Hielscher42-477-31236
2.6 KM · Geosouthern Operating II, LLC · Section with this well →
| Wilcox | 4,592 | -4,135 |
| Austin Chalk | 12,570 | -12,113 |
| Caprock | — |
Hielscher42-477-31235
2.6 KM · Geosouthern Operating II, LLC · Section with this well →
| Wilcox | 4,609 | -4,150 |
| Austin Chalk | 12,641 | -12,182 |
| Caprock | — |
Thorpe42-477-31080
2.8 KM · Wildhorse Resources Mngt Co, LLC · Section with this well →
| Caprock | 2,410 | -1,930 |
| Wilcox | 4,265 | -3,785 |
| Pecan Gap | 11,558 | -11,078 |
| Austin Chalk | 12,697 | -12,217 |
Draeger42-477-31081
2.8 KM · Wildhorse Resources Mngt Co, LLC · Section with this well →
| Caprock | 2,410 | -1,929 |
| Wilcox | 4,475 | -3,994 |
| Pecan Gap | 11,466 | -10,985 |
| Austin Chalk | 12,630 | -12,149 |
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/47731060, documented in the API reference.