Every figure this model derived for SVRN, 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 2024-12-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
18,906,000
PaymentsToAcquirePropertyPlantAndEquipment
2024-12-31
cash
25,765,000
CashAndCashEquivalentsAtCarryingValue
2025-06-30
current assets
28,927,000
AssetsCurrent
2025-06-30
current liabilities
4,104,000
LiabilitiesCurrent
2025-06-30
equity
74,067,000
StockholdersEquity
2025-06-30
interest expense
109,000
InterestExpenseNonoperating
2024-12-31
ocf
-3,530,000
NetCashProvidedByUsedInOperatingActivities
2024-12-31
revenue
25,702,000
Revenues
2024-12-31
sbc
0
AllocatedShareBasedCompensationExpense
2021-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
SVRN on one particular measure came for.
Ratio
Value
cash operating margin
-42.2
current ratio
8.91
current ratio reported
7.05
deferred revenue growth
-53.88
dilution pct
121.01
fcf margin
-87.29
interest cover
-165.55
operating margin
-70.21
owner earnings margin
-87.29
revenue growth
35.58
revenue growth per share
-38.65
roic
-29.51
rule of 40
-34.63
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about SVRN's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
revenue period ends 2024-12-31 (607 days ago) - the tag chain found nothing recent, so treat this row as unscored
no current stock compensation tagged (last tagged 2021-12-31); treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
share count is from 2025-06-30 (426 days old, balance sheet); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
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 (worst year, gross margin stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
growth rests on 3 of 4 inputs; not tagged: sustained growth
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