Every figure this model derived for LBRT, the value it took, and
the element in the company's own XBRL it was read from — so any of it can be checked
against the filing rather than taken on trust.
As at 2026-06-30.
The figures, and where each came from
This is the part no other screener shows. Each figure below names the XBRL element it
was read from, so it can be checked against the filing itself.
Figure
Value
XBRL tag
As at
capex
704,913,000
PaymentsToAcquireProductiveAssets
2026-06-30
cash
555,359,000
CashAndCashEquivalentsAtCarryingValue
2026-06-30
current assets
1,566,676,000
AssetsCurrent
2026-06-30
current liabilities
788,742,000
LiabilitiesCurrent
2026-06-30
equity
1,963,754,000
StockholdersEquity
2026-06-30
interest expense
31,686,000
InterestExpenseNonoperating
2026-06-30
ocf
388,333,000
NetCashProvidedByUsedInOperatingActivities
2026-06-30
revenue
4,195,914,000
Revenues
2026-06-30
sbc
33,740,000
ShareBasedCompensation
2026-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
LBRT on one particular measure came for.
Ratio
Value
cash operating margin
13.29
current ratio
1.99
current ratio reported
1.99
deferred revenue growth
-100.0
dilution pct
-2.38
ebit cagr
-47.4
ebit yoy
-72.02
fcf margin
-7.54
growth cv
1.4
interest cover
1.66
net debt ebitda
1.93
operating margin
1.25
owner earnings margin
-8.35
revenue growth
2.29
revenue growth per share
4.78
roic
1.39
rule of 40
3.54
sbc pct revenue
0.8
What to be careful about
What this model itself distrusts about LBRT's figures. Written by the
derivation as it ran, not added afterwards.
no market cap; set `market_cap` in overrides.yaml
gross profit not tagged; rebuilt from Revenues - CostOfGoodsAndServicesSold
no forward EPS estimate; growth rests on filings only. Analyst consensus is not published in XBRL, so it has to be fetched from a data provider or set by hand in overrides.yaml as `eps_growth_2y`
valuation DROPPED from the total: only 0 of 2 inputs could be computed (ev sales, ev owner earnings not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
durability rests on 3 of 4 inputs; not tagged: contracted coverage