Every figure this model derived for RYN, 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-03-31.
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
0
PaymentsToAcquireOtherPropertyPlantAndEquipment
2024-12-31
cash
681,660,000
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
895,736,000
AssetsCurrent
2026-03-31
current liabilities
354,127,000
LiabilitiesCurrent
2026-03-31
equity
5,329,356,000
StockholdersEquity
2026-03-31
interest expense
34,258,000
InterestExpenseNonoperating
2026-03-31
ocf
263,545,000
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
678,351,000
Revenues
2026-03-31
sbc
24,136,000
ShareBasedCompensation
2026-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
RYN on one particular measure came for.
Ratio
Value
cash operating margin
9.1
current ratio
2.73
current ratio reported
2.53
deferred revenue growth
48.14
dilution pct
4.35
ebit cagr
-36.67
ebit yoy
-89.42
fcf margin
38.85
interest cover
1.1
net debt ebitda
36.96
operating margin
5.55
owner earnings margin
35.29
revenue growth
-29.13
revenue growth per share
-32.08
roic
0.44
rule of 40
-23.58
sbc pct revenue
3.56
What to be careful about
What this model itself distrusts about RYN's figures. Written by the
derivation as it ran, not added afterwards.
no current capital expenditure tagged (last tagged 2024-12-31); treated as zero, so free cash flow is overstated and equals operating cash flow
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-05-01 (121 days old, dei cover page); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
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