Every figure this model derived for HERE, 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-06-30.
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
432,000
PaymentsToAcquirePropertyPlantAndEquipment
2025-06-30
cash
142,367,000
CashAndCashEquivalentsAtCarryingValue
2025-06-30
current assets
183,252,000
AssetsCurrent
2025-06-30
current liabilities
85,713,000
LiabilitiesCurrent
2025-06-30
equity
112,931,000
StockholdersEquity
2025-06-30
interest expense
7,000
InterestPaidNet
2025-06-30
ocf
25,671,000
NetCashProvidedByUsedInOperatingActivities
2025-06-30
revenue
380,478,000
Revenues
2025-06-30
sbc
2,861,000
ShareBasedCompensation
2025-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
HERE on one particular measure came for.
Ratio
Value
cash operating margin
15.52
current ratio
3.49
current ratio reported
2.14
deferred revenue growth
-37.3
dilution pct
-2.85
ebit yoy
6.7
fcf margin
6.63
interest cover
7915.14
operating margin
14.56
owner earnings margin
5.88
revenue growth
-27.15
revenue growth per share
-25.01
rule of 40
-12.58
sbc pct revenue
0.75
What to be careful about
What this model itself distrusts about HERE'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 2025-06-30 (426 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.
invested capital is -29M (cash exceeds equity plus debt), so return on capital is unbounded rather than undefined; scored as maximal
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: worst year
growth rests on 3 of 4 inputs; not tagged: sustained growth