TEXAS · WELLS · GONZALES COUNTY · API 42-177-32113 · DISTRICT 01
Hansen Kullin Unit #2H
Gonzales County · Eagleville (Eagle Ford-1) field · Producing · Horizontal
- Permitted field
- Eagleville (Eagle Ford)
Hansen Kullin Unit #2H (API 42-177-32113) is a horizontal well in Gonzales County operated by Eog Resources Inc., completed December 18, 2010 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued August 5, 2010, permitted to 11,076 ft.
Completion filings report 7 formation tops, including Wilcox, Midway, Navarro, Olmos.
Its 2 leases have reported 3.05M barrels of oil and 5.5M mcf of gas since November 2010, last reporting volume in April 2026. The leases carry 14 wells, so these are lease totals, not this well alone.
Operator of record
- Based in
- Midland, TX
- P-5 status
- Active (A)
- P-5 last filed
- Oct 2, 2025
- Permits on file
- 16,354
- Phone
- (713) 651-7000
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | EOG Resources Inc. |
| Production reports | EOG Resources, Inc.through Apr 2026 |
| Latest permit | EOG Resources, Inc.Aug 5, 2010 |
- 11,076
- total depth, ft
- 1
- permits on file
- Aug 5, 2010
- last permit issued
- Dec 18, 2010
- completed
- 3.05M
- cumulative oil, bbl
- 5.5M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Dec 2010 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Dec 18, 2010
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active – Extension (X)
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 14 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Hansen Kullin Unit O-1-15402 | Eagleville (Eagle Ford-1) | EOG Resources, Inc. | 12 | 3.05M | 5.5M | Dec 2010 – Apr 2026 |
| Hansen-Kullin Unit O-2-9634 | Eagleville (Eagle Ford) | EOG Resources, Inc. | 2 | 0 | 0 | Nov 2010 – — |
Oil, barrels lease total
Last 12 months 39,297 · prior 12 42,077(-7%)
Gas, mcf lease total
Last 12 months 114,276 · prior 12 101,318(+13%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1EOG Resources, Inc.Dec 2010 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 700189-99 | Drill | EOG Resources, Inc. | Aug 3, 2010 | Aug 5, 2010 | Nov 7, 2010 | 12,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Dec 18, 2010 | Hansen Kullin Unit O-1-15402 | Eagleville (Eagle Ford-1) | EOG Resources Inc. | Producing | 11,076 |
| Nov 26, 2010 | Hansen-Kullin Unit O-2-9634 | Eagleville (Eagle Ford) | EOG Resources Inc. | Not on Schedule | — |
Formation tops
As filed on W-2/G-1. Subsea from 303 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Wilcox | 3,372 | -3,069 |
| Midway | 7,249 | -6,946 |
| Navarro | 8,449 | -8,146 |
| Olmos | 9,014 | -8,711 |
| Anacacho | 10,076 | -9,773 |
| Anacacho | 10,149 | -9,846 |
| Austin Chalk | 10,534 | -10,231 |
| Eagle FordEAGLEFORD | 10,867 | -10,564 |
| Eagle FordEAGLEFORD | 10,953 | -10,650 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 11,530 | 14,870 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 2,493 | 12.25 | 760 S |
| 5.5 | 15,013 | 8.75 | 2,310 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 | Jan 13, 2012 | Jan 13, 2011 | Yes |
| 00 | Jan 12, 2012 | Dec 16, 2010 | Yes |
Well logs
1 log loaded from the RRC's log index, the latest received Nov 6, 2013. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| RESISTIVITYSpans Wilcox, Midway, Navarro, Olmos, Anacacho, Austin Chalk, Eagle Ford | TIFF | 2,504 to 15,013 | Nov 6, 2013run Nov 24, 2010 | 1.34 |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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-177-32113 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-177-32113 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search 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/17732113, documented in the API reference.