WELL · 42-447-36868 · DISTRICT 8

Wbrr 233 #112

Y

Throckmorton County · Throckmorton County Regular field · Producing  · Vertical

Wbrr 233 #112 (API 42-447-36868) is a well in Throckmorton County operated by Okie Operating Company Ltd., completed May 5, 2026 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued April 21, 2026, permitted to 999 ft.

Completion filings report 10 formation tops, including Frye - Disposal, Cook - Disposal, Caddo, Coleman Junction.

Its lease has reported 212K barrels of oil since October 2011, last reporting in July 2026. The lease carries 47 wells, so these are lease totals, not this well alone.

Operator of record

Okie Operating Company Ltd.

Tulsa, OK · P-5 Y, filed Apr 4, 2026 · 8 permits on file · (918) 582-2555

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOkie Operating Company Ltd.
Production reportsOkie Operating Company, Ltd.through Apr 2026
Latest permitOkie Operating Company, Ltd.Apr 21, 2026
999
total depth, ft
1
permits on file
Apr 21, 2026
last permit issued
May 5, 2026
completed
212K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2011 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 5, 2026
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 47 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Wbrr 233 O-8-30929Throckmorton County RegularOkie Operating Company, Ltd.47212K0Oct 2011 – Jul 2026

Oil, barrels lease total

Last 12 months 14,740 · prior 12 16,033(-8%)

01K2K202420252026

Chain of custody

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

  1. 1Hilltex Operating Company, LLCJan 2012 → Aug 2016
  2. 2Drake Petroleum, LLCSep 2016 → Dec 2021
  3. 3Okie Operating Company, Ltd.Jan 2022 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
914927-99DrillOkie Operating Company, Ltd.Apr 15, 2026Apr 21, 2026Apr 29, 2026999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-30929————

Formation tops

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

FormationMD ftSubsea
Frye - Disposal400997
Cook - Disposal760637
CaddoCADDO - DISPOSAL——
Coleman Junction——
Ellenburger——
Flippen - Disposal——
Hickory - Disposal——
MississippianMISSISSIPPIAN - DISPOSAL——
San AndresSAN ANDRES - DISPOSAL——
WolfcampWOLFCAMP - DISPOSAL——

Perforations

Perforated and open-hole intervals.

FromToType
761763Perforated
772782Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.58286.75180 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
00Jun 8, 2026May 15, 2026Yes

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