Every figure this model derived for GRAN, 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
139,153
PaymentsToAcquirePropertyPlantAndEquipment
2025-03-31
cash
1,451,526
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
2,583,153
AssetsCurrent
2026-03-31
current liabilities
4,786,026
LiabilitiesCurrent
2026-03-31
equity
7,253,334
StockholdersEquity
2026-03-31
ocf
-734,152
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
1,807,643
Revenues
2026-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
GRAN on one particular measure came for.
Ratio
Value
cash operating margin
-181.0
current ratio
0.85
current ratio reported
0.54
deferred revenue growth
776.82
dilution pct
65.94
fcf margin
-48.31
operating margin
-182.98
owner earnings margin
-48.31
revenue growth
-58.34
revenue growth per share
-74.89
roic
-45.04
rule of 40
-241.31
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about GRAN's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
no current stock compensation tagged; treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-03-31 (152 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 debt and no profit, so interest cover cannot be measured; scored on cash runway instead: 1M of net cash against a 1M annual burn is 1.7 years
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
growth rests on 3 of 4 inputs; not tagged: sustained growth