Every figure this model derived for GRVY, 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.
The figures themselves rather than their scores — what somebody looking up
GRVY on one particular measure came for.
Ratio
Value
cash operating margin
18.25
current ratio
6.02
current ratio reported
6.02
deferred revenue growth
93.9
ebit yoy
-46.76
fcf margin
15.56
interest cover
632.47
operating margin
17.05
owner earnings margin
15.56
revenue growth
-30.97
revenue growth per share
-30.97
roic
19.88
rule of 40
-13.92
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about GRVY's figures. Written by the
derivation as it ran, not added afterwards.
newest fact in the filing is 2024-12-31 (1y old); this company's data is not usable and the scores below should be ignored
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 2009-12-31); treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
reports in KRW and no currency is recorded for its share price, so the two cannot be shown to match. The price refresh records one; until it has run for this company the multiples are left out rather than assumed comparable
share count is from 2025-12-31 (242 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.
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`
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 rests on 3 of 4 inputs; not tagged: contracted coverage