Every figure this model derived for WKEY, 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 2025-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
743,000
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
439,276,000
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
455,778,000
AssetsCurrent
2025-12-31
current liabilities
35,266,000
LiabilitiesCurrent
2025-12-31
equity
45,916,000
StockholdersEquity
2025-12-31
interest expense
224,000
InterestExpenseDebt
2025-12-31
ocf
-32,362,000
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
19,289,000
Revenues
2025-12-31
sbc
8,347,000
ShareBasedCompensation
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
WKEY on one particular measure came for.
Ratio
Value
cash operating margin
-200.09
current ratio
13.61
current ratio reported
12.92
deferred revenue growth
352.3
fcf margin
-171.63
growth cv
2.46
interest cover
-212.92
operating margin
-247.26
owner earnings margin
-214.9
revenue growth
62.43
revenue growth per share
62.43
rpo growth
28.54
rule of 40
-184.83
sbc pct revenue
43.27
What to be careful about
What this model itself distrusts about WKEY's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
no market cap; set `market_cap` in overrides.yaml
share count is from 2022-12-31 (1338 days old, weighted average diluted); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
no usable diluted share count, so growth is measured on total revenue rather than per share; a company issuing shares to fund that growth reads better than it is
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`
quality rests on 4 of 5 inputs; not tagged: roic
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