Friday, February 16, 2018

Random Update Of Two XTO Wells In Lost Bridge After Neighboring Well Fracked -- February 16, 2018

From an earlier post:
August 28, 2017: check #19960, #18189 at end of 2017. Neighboring wells just fracked (31199, 31200, 31201, 31202)
  • 31199, 1,838, XTO, Kaye Federal 13X-3H, Lost Bridge, t5/61 (sic, probably 6/17); cum 94K 12/17; (#19960, #18189); update here, #19960 with huge jump in production; #18189 still off-line;
So, let's check #18189 and #19960.

#18189, has just come back on-line; too early to say what it might do once it's back up to speed; no evidence at FracFocus that this well has been re-fracked, API: 33-025-00943;
Monthly Production Data:
PoolDateDaysBBLS OilRunsBBLS WaterMCF ProdMCF SoldVent/Flare
BAKKEN12-201715655610165561193359
BAKKEN11-20170000000
BAKKEN10-20170000000
BAKKEN9-20170000000

Now, take a look at #19960:
  • 19960, 1,666, XTO, Kaye 43X-4, API: 33-025-01222; Lost Bridge, t12/11; cum 509K 12/17; no evidence in FracFocus that it has been re-fracked and no sundry form suggesting it has been re-fracked; FracFocus link here. See if you can find the jump in production; to me, it is so huge, this well must have been re-fracked, but no data to suggest that (yet), although initial jump dropped back quickly; maybe just a one-month peculiarity after coming back on-line (I certainly can't explain it but nice for the mineral owners):
Monthly Production Data:
PoolDateDaysBBLS OilRunsBBLS WaterMCF ProdMCF SoldVent/Flare
BAKKEN12-201730670270854237615918804055
BAKKEN11-20173016689158909530308128410
BAKKEN10-20177107610308081033895115
BAKKEN9-20170000000
BAKKEN8-20170000000
BAKKEN7-20170000000
BAKKEN6-201700650000
BAKKEN5-20170000000
BAKKEN4-201761651063563553480
BAKKEN3-2017316937709622481261174174913
BAKKEN2-201761087734223199819510


No comments:

Post a Comment

Note: Only a member of this blog may post a comment.