WELL · 42-253-35007 · DISTRICT 7

Kiser #2

Y

Jones County · Jones County Regular field · Producing  · Vertical

Kiser #2 (API 42-253-35007) is a well in Jones County operated by Bluff Creek Petroleum LLC, completed June 23, 2008 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued April 25, 2008, permitted to 2,999 ft.

It was permitted by Cottonwood Petroleum CO. and has since transferred to Bluff Creek Petroleum LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Dothan, Stockwether, Saddlecreek, Flippen.

Its lease has reported 18.8K barrels of oil since June 2008, last reporting in July 2026.

Operator of record

Bluff Creek Petroleum LLC

Permitted by Cottonwood Petroleum Co.; the EWA schedule now lists a different operator.

Abilene, TX · P-5 Y, filed Mar 4, 2026 · 117 permits on file · (325) 668-7848

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBluff Creek Petroleum LLC
Production reportsBluff Creek Petroleum, LLCthrough Apr 2026
Latest permitCottonwood Petroleum Co.Apr 25, 2008

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

2,999
total depth, ft
1
permits on file
Apr 25, 2008
last permit issued
Jun 23, 2008
completed
18.8K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2008 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 23, 2008
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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Kiser O-8-30121Jones County RegularBluff Creek Petroleum, LLC118.8K0Jun 2008 – Jul 2026

Oil, barrels lease total

Last 12 months 910 · prior 12 777(+17%)

050100150202420252026

Chain of custody

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

  1. 1Cottonwood Petroleum Co.Jun 2008 → Jun 2009
  2. 2Bluff Creek Petroleum, LLCJul 2009 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
659232-99DrillCottonwood Petroleum Co.Apr 9, 2008Apr 25, 2008Jun 11, 20082,999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-30121————

Formation tops

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

FormationMD ftSubsea
Dothan1,670-54
Stockwether1,718-102
Saddlecreek1,782-166
Flippen1,910-294

Perforations

Perforated and open-hole intervals.

FromToType
1,8141,818Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251211185 S
4.51,9626.75300 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
00Oct 27, 2008Jul 1, 2008Yes
00Sep 16, 2008——

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