Every figure this model derived for FROG, 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-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
6,563,000
PaymentsToAcquirePropertyPlantAndEquipment
2026-06-30
cash
824,486,000
CashAndCashEquivalentsAtCarryingValue
2026-06-30
current assets
1,017,682,000
AssetsCurrent
2026-06-30
current liabilities
476,636,000
LiabilitiesCurrent
2026-06-30
equity
960,706,000
StockholdersEquity
2026-06-30
ocf
176,264,000
NetCashProvidedByUsedInOperatingActivities
2026-06-30
revenue
234,583,000
SellingAndMarketingExpense
2026-06-30
sbc
161,007,000
ShareBasedCompensation
2026-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
FROG on one particular measure came for.
Ratio
Value
cash operating margin
48.7
current ratio
8.13
current ratio reported
2.14
deferred revenue growth
35.17
dilution pct
5.94
fcf margin
72.34
growth cv
0.52
operating margin
-29.45
owner earnings margin
3.71
revenue growth
12.15
revenue growth per share
5.86
roic
-40.07
rpo growth
38.24
rule of 40
-17.31
sbc pct revenue
68.64
What to be careful about
What this model itself distrusts about FROG's figures. Written by the
derivation as it ran, not added afterwards.
no market cap; set `market_cap` in overrides.yaml
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
resilience rests on 2 of 3 inputs; not tagged: interest cover