Every figure this model derived for LBRA, 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
240,517
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
442,279
CashAndCashEquivalentsAtCarryingValue
2026-06-30
current assets
29,872,177
AssetsCurrent
2026-06-30
current liabilities
71,309,802
LiabilitiesCurrent
2026-06-30
equity
-37,607,051
StockholdersEquity
2026-06-30
interest expense
8,146,486
InterestExpenseNonoperating
2026-06-30
ocf
3,437,501
NetCashProvidedByUsedInOperatingActivities
2026-06-30
revenue
28,117,921
Revenues
2026-06-30
sbc
0
ShareBasedCompensation
2020-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
LBRA on one particular measure came for.
Ratio
Value
cash operating margin
23.44
current ratio
0.42
current ratio reported
0.42
deferred revenue growth
-83.6
dilution pct
36430.56
fcf margin
11.37
growth cv
1.32
interest cover
0.64
net debt ebitda
3.43
operating margin
18.48
owner earnings margin
11.37
revenue growth
81.14
revenue growth per share
-99.5
rule of 40
99.63
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about LBRA's figures. Written by the
derivation as it ran, not added afterwards.
no current stock compensation tagged (last tagged 2020-12-31); treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
invested capital is -15M (cash exceeds equity plus debt), so return on capital is unbounded rather than undefined; scored as maximal
gross profit not tagged since 2017-09-30; rebuilt from Revenues - CostOfRevenue
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