Every figure this model derived for OWL, 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.
The figures themselves rather than their scores — what somebody looking up
OWL on one particular measure came for.
Ratio
Value
cash operating margin
41.72
current ratio
11.78
current ratio reported
11.78
dilution pct
18.54
ebit yoy
11.07
fcf margin
44.26
growth cv
1.03
interest cover
2.89
net debt ebitda
6.85
operating margin
16.91
owner earnings margin
20.31
revenue growth
14.19
revenue growth per share
-3.67
roic
7.08
rule of 40
31.1
sbc pct revenue
23.95
What to be careful about
What this model itself distrusts about OWL's figures. Written by the
derivation as it ran, not added afterwards.
operating income last tagged 2020-12-31, 2007 days before the revenue period (2026-06-30); dropped rather than divided by current revenue
no operating income tagged; derived as revenue minus CostsAndExpenses
no market cap; set `market_cap` in overrides.yaml
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 DROPPED from the total: only 2 of 4 inputs could be computed (contracted coverage, gross margin stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
2 of 5 dimensions could not be measured (valuation, durability -- 35% of the model), so this row is not comparable with the others; its total rests on what was left