OPERATORS · RRC 103155 · P-5 STATUS Y
Bright Star Expl, LLC
Oklahoma City, OK · most active in Hopkins County
Watch this operatorBright Star Expl, LLC was issued 5 drilling permits in the past 12 months, after a quiet prior year, across 2 counties led by Hopkins with 3. 0% were horizontal.
None were issued in the past 90 days.
5 drilling permits have been issued to this operator number since 2025; its P-5 organization report was last filed February 4, 2026.
- 5
- permits, last 12 months
- —
- vs prior 12 months (0)
- 2
- counties, 12 months
- 0
- producing wells, of 0 of record
- 0
- leases it reports
- 0%
- horizontal, 12 months
WINDOWS ON THE RRC ISSUE DATE · COMPUTED OCT 29, 2026
From permit to spud
FROM THE DATES ON ITS W-1 PERMITS · ALL TIME
A permit is a plan, not a well. These figures count only permits old enough to have spudded, six months and more, and read the spud, cancel, and expiry dates the RRC records on each one.
- 0%
- spud rate · 0 of 5 mature permits
- —
- median days permit to spud
- 0
- spuds, last 180 days
- 0%
- cancelled · 0 permits
- 5
- expired undrilled
- 5
- permits a year over 1 active year
Permits issued by month
LAST 1 MONTHS · BY ISSUE DATE
Last 12 months 5
Where
Counties by permits in the last 12 months, with all-time permits and current wells of record there.
All 5 permits, searchable → · Leases it reports → · On the map →
Formations in its completed wells
Tops reported on completion filings for wells it operates. RRC wellbore file. About tops →
| Formation | Wells | Permitted last 3 yrs |
|---|---|---|
| No completion tops on file. | ||
Production by month
PDQ LEASE REPORTS · REPORTED THROUGH APR 2026
Barrels on leases where this operator filed the production report. Lease-level by design; the latest months are revised upward as late reports arrive. How production is reported →
- 0
- bbl oil, last 12 reported months
- —
- vs the 12 months before
- 0
- mcf gas incl. casinghead, last 12
- 0
- bbl oil since reporting began
No lease production reported under this operator number in the last three years.
Beyond the permit record
RRC wellbore file
Wells of record
- 0
- on the schedule
- 0
- producing
- 0
- shut in
- 0
- injection
- 0
- temp. abandoned
- 0
- plugged
How it got them
- 0
- permitted itself
- 0
- acquired from others
- 0
- permitted, now run by others
Acquired means the well's permit names a different operator than the schedule does today. Transfers and operator numbers →
Permit types
Last 12 months against the prior 12, and all time. A type opens the permit history filtered to it. What the types mean →
P-5 organization report
As registered with the RRC. About the P-5 →
- Registration
- Status code Y
- Last filed Feb 4, 2026
- Address
- PO Box 890134
- Oklahoma City, OK 73189
- (405) 850-5447
- Officers and agents
- Davis, Matthew · Texas Resident Agent
- Humphers, Jeremy · Managing Member
- Galvanic Fund II, LLLP · Member
Latest permits
NEWEST FIRST BY ISSUE DATE · FILED OR ON WELLS IT NOW OPERATES
| Permit | Seen | Issued | Operator | County | Lease / well | Depth | API |
|---|---|---|---|---|---|---|---|
| 911709 | Nov 19, 2025 | Nov 19, 2025 | Bright Star Exploration, LLC | Hopkins | Kempenaar #1 | 14,000 | 22330524 |
| 911708 | Nov 19, 2025 | Nov 19, 2025 | Bright Star Exploration, LLC | Rains | Tilger #1 | 13,000 | 37930162 |
| 911707 | Nov 19, 2025 | Nov 19, 2025 | Bright Star Exploration, LLC | Hopkins | Willis W Stewart #1 | 11,100 | 22330068 |
| 911707 | Nov 19, 2025 | Nov 19, 2025 | Bright Star Exploration, LLC | Hopkins | Willis W Stewart #1 | 13,500 | 22330068 |
| 911705 | Nov 19, 2025 | Nov 19, 2025 | Bright Star Exploration, LLC | Rains | Potts #1 | 13,700 | 37930004 |
About this data
Registration from the RRC P-5 organization report, refreshed weekly. Permits from the OGA049M master and daily daf420 files; wells of record from the EWA wellbore schedule; production from PDQ lease reports at the last vintage; disposal from UIC permits and H-10 reports. Summary figures are rebuilt nightly.
Developers: this page as JSON is GET /v1/data/operators/tx/103155, documented in the API reference.